1000 Thanks to Edmund!
It dies after saying "irq still active". (To get that message I'm using the patch that Michael Hohmuth posted to the list on July 25.) I think I may have found a bug in the SANITY code in linux22/arch/l4-i386/kernel/irq.c, by the way. See below.
I remember, I've ever seen same message & following crash, thanks for the patch.
What I have been doing is telling GDB "symbol-file .../vmlinux" to inspect what's happening in Linux, then "symbol-file .../kernel.image" to go back to inspecting Fiasco. There's probably some way of defining macros to make that switching a bit easier.
Ahh, Thanks! Following your instruction, I could trace L4-Linux. I see: L4-Linux is loaded onto real wired memory without virtualization, thus, the kernel-debugger can watch and fix the text/data of L4-Linux directly.
suzuki