Hey all, quick question. I'm working on a test to catch when an application crashes, and launch another executable (eventually crash reporter).
I'm exhibiting strange behavior - whenever I quit the application normally, the information I'm getting back about what happened and why it stopped is always a signal, but the signal is never the same. So a couple questions: -Where can I find all of the signal definitions? I've found up to about 50 of them, but I'm getting signals in the hundreds. -Would you be willing to skim this code real quick? (http://pastebin.org/859983). It's pretty short. The focus is the main() function. There are a couple printf's in there just so I could figure out which signals are being reported. I'm getting all kinds. Here's a couple of session outputs. -- error: Interrupted system call waited: 7095 signal: 55 -- error: Interrupted system call waited: 7136 signal: 96 -- error: Interrupted system call waited: 7151 signal: 111 I get these from quitting the application normally (cmd+q) or going to the menu>quit option. Since I'm not able to find where some of these signals are defined I'm not sure what they are. Alternatively, I found a list of signals that come directly from the kernel and are sent to processes: http://www.mugginsoft.com/content/how-crash-cocoa-app-testing-purposes-abnormal-termination http://www.opensource.apple.com/source/xnu/xnu-1228.3.13/bsd/uxkern/ux_exception.c?f=text would it be valid to check against those and ignore the rest? Thanks in advance! _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
