Enabling kernel parameter print-fatal-signals worked out nicely: > / # echo 1 >/proc/sys/kernel/print-fatal-signals > / # trap > trap/82: potentially unexpected fatal signal 4. > > > Format 04 Vector: 009c PC: 4052812e Status: 0000 Not tainted > ORIG_D0: ffffffff D0: 405285c8 A2: 40529f64 A1: 405284dc > A0: 40528128 D5: 40528524 D4: 00000000 > D3: 00000000 D2: 00000001 D1: 0000002f > USP: 40529f10
FYI. The messages do not get sent to /var/log/messages. I don't know why. That would be more useful. I am still puzzled, though, why uClinux is silent when a program is aborted when it receives an unhandled fatal signal. Mainline Linux (really the shell?) prints out a message like > [root@atompc sdk]# ./SIGILL > Illegal instruction (SIGILL.c is the example program from http://en.wikipedia.org/wiki/SIGILL.) After a reboot of uClinux, I get nothing > / # SIGILL I have to enable print-fatal-signals as before to see anything: > / # echo 1 >/proc/sys/kernel/print-fatal-signals > / # SIGILL > SIGILL/79: potentially unexpected fatal signal 4. > > > Format 04 Vector: 002c PC: 4052e544 Status: 0000 Not tainted > ORIG_D0: ffffffff D0: 4052e544 A2: 4052ff60 A1: 4052e4ec > A0: 4052e544 D5: 4052e524 D4: 00000000 > D3: 00000000 D2: 00000001 D1: 0000002f > USP: 4052ff04 Is this a uClinux thing? Or, a BusyBox (my uClinux shell) thing? 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
