Hi,
Adam Lackorzynski wrote:
On Fri Aug 11, 2006 at 14:39:32 +0200, Andreas Niederl wrote:
[...]
Now the system stops after printing out the message 'l4lx | l4lx_thread_create: Created thread 0e.0b (IRQ17)'. When using l4io as omega0 server it stops after this message: l4lx_irq_dev_startup_virt(17) unimplemented
Yes, unimplemented, I'm sorry. I added that to my todo list, should be low hanging stuff.
What about the stop after I got the first message using one thread per IRQ with the rmgr way? Is it a known problem or perhaps caused by some misconfiguration on my side?
Ctrl-C still doesn't work on my serial console, so I'm not able to debug this.
I don't understand. Who should get that Ctrl-C?
Well, perhaps I've confused something. I want to get into the JDB and as on Fiasco-UX this is done by typing Ctrl-C, I thought it would be the same on Fiasco and the serial line.
The JDB manual states that with the option '-serial_esc' Fiasco enters JDB on serial receive interrupts. Now I have no idea how to generate the needed interrupt.
Is gdb suitable for this kind of debugging? I could not find much information on this topic on the internet.
gdb is not really suited for multi address space debugging. Fiasco has a nice built-in debugger which gives you thread states, back traces, present and ready lists, various forms of tracing and logging etc.
I see.
Regards, Andi