Re: Invalid Opcode on ia32, Pistachio 0.4

Hi!

Sebastian Reichelt wrote:
> In case the kernel debugger is not compiled in, won't enter_kdebug()
> return immediately? I believe you cannot enable it in (potential)
> production systems anyway because any user-level program can execute
> L4_KDB_Enter. I may be overlooking something, though.

>From /source/kernel/include/debug.h:

65 #if defined(CONFIG_DEBUG)

	[...]

118 #else /* !CONFIG_DEBUG */
119
120 /*
121  * Define all functions as empty.
122  */
123
124 # define init_console()
125 # define printf(fmt, args...)   do { } while (false)
126 # define enter_kdebug(x)        do { } while (true)
127 # define UNIMPLEMENTED()        do { } while (true)
128 # define ASSERT(x)              do { } while (false)
129 # define WARNING(fmt, args...)  do { } while (false)
130 # define TRACE(x...)            do { } while (false)
131 # define TRACEF(x...)           do { } while (false)
132 # define spin_forever(x...)     do { } while (true)
133 # define spin(x...)             do { } while (false)
134
135 #endif /* CONFIG_DEBUG */

This looks like a crash..

> By the way, the same issue exists with user-level code touching the
> kernel's region of the virtual address space.
Yeah, I noticed this, too.


Best regards,

Alexander Wieder