On Wed, Oct 3, 2012 at 11:38 PM, Larry Baker <ba...@usgs.gov> wrote: > > It would be pretty easy to just add a whole bunch of debug trace in > > the kernel when you get this - just for debugging purposes of course. > > Probably makes no sense for a user space process to catch the SIGILL > > in this case. You are out of stack and drastic action is needed. > > I'm still looking for the conditions it takes to have something like > show_registers() in arch/m68k/kernel/traps.c called when the trap occurs.
The registers are only printed for exceptions caused in kernel mode. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev