Geert, On Oct 3, 2012, at 10:00 PM, Geert Uytterhoeven wrote:
>> 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. The print-fatal-signals kernel parameter can be enabled which is consulted by get_signal_to_deliver() in kernel/signal.c to decide whether to dump registers: > if (sig_kernel_coredump(signr)) { > if (print_fatal_signals) > print_fatal_signal(regs, info->si_signo); > /* > * If it was able to dump core, this kills all > * other threads in the group and synchronizes with > * their demise. If we lost the race with another > * thread getting here, it set group_exit_code > * first and our do_group_exit call below will use > * that value and ignore the one we pass it. > */ > do_coredump(info->si_signo, info->si_signo, regs); > } >From Documentation/kernel-parameters.txt: > print-fatal-signals= > [KNL] debug: print fatal signals > > If enabled, warn about various signal handling > related application anomalies: too many signals, > too many POSIX.1 timers, fatal signals causing a > coredump - etc. > > If you hit the warning due to signal overflow, > you might want to try "ulimit -i unlimited". > > default: off. Tomorrow I will find out if this will produce what I am looking for. > 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 Larry Baker US Geological Survey 650-329-5608 ba...@usgs.gov _______________________________________________ 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