On Thu, May 22, 2008 at 09:49:32PM +0200, vincent-perrier wrote: > si_errno and si_code are both zeros, I am sad to say.
That doesn't necessarily mean there's no information. zero might mean the signal came from a process. Can you strace it? Also, send me the full siginfo? There might be something in .si_pid and .si_user. As for your gdb problem: > Locating the top of the address space ... > Program received signal SIGSEGV, Segmentation fault. > 0x0806a1cd in page_ok (page=0) at > arch/um/os-Linux/sys-i386/task_size.c:31 UML is causing segfaults on purpose, which gdb doesn't really expect. Do (gdb) handle SIGSEGV pass nostop noprint to tell gdb to ignore them. Jeff -- Work email - jdike at linux dot intel dot com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user