On May 17, 2013, at 5:25 AM, Quinn The Eskimo! wrote:
My best guess is that you have your own in-process crash reporter. That's a bad idea in general, and seems to be the cause of this hang. If you didn't catch the signal, it would've been caught by the system-wide out-of-process crash reporter, which would give you a nice crash log.
I understand the desire for the crash log, especially for a server thingy under development. But it's safer, and probably even easier, to build an out-of-process reporter. Launch a child process, and set it up correctly to be notified of its parent's death. All that process has to do is find the latest crash report at launch, then at parent death, if the process exited abnormally, wait for a newer crash log to appear and do whatever you want with it. Sorry to not offer more details, but I did this 10 years ago and my recall is hazy about the inner workings. I just get the reports ;-) Note that I said "all that process HAS to do"--it's not all it CAN do, you can have it monitoring and reporting whatever else you want, logs, resources usage... -- Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com