Re: NSTask prevents crashreporter from running when child process crashes?
Re: NSTask prevents crashreporter from running when child process crashes?
- Subject: Re: NSTask prevents crashreporter from running when child process crashes?
- From: Dave Camp <email@hidden>
- Date: Tue, 24 Apr 2007 09:37:14 -0700
Have you tried adding a Logs folder? I've found CrashReporter to not
be terribly smart in that regard...
Dave
On Apr 24, 2007, at 8:19 AM, Markus Hanauska wrote:
It could do that, but that's not what it does either.
Actually /var/root/Library does not even have a Logs folder on my
system.
I had expected it to write the crash log to /Library/Logs/
CrashReporter as other system services do as well, but that's also
not what it is doing. If I call it from command line and it
crashes, that's where it writes the CrashReport to. But as NSTask,
I see no crashlog in any location. Ideas?
On 2007-04-24, at 16:11, Michael Watson wrote:
If the daemon is SUID root, wouldn't it write crash log data to
root's Library folder?
--
m-s
On 24 Apr, 2007, at 04:19, Markus Hanauska wrote:
Hello everyone,
I have a little, but very annoying issue. We have a small daemon
application (written in C), that runs with SUID Bit set (owned by
root). If this app has been called from command line and crashes,
it writes a crash report, as every other app, too. But when we
start exactly the same application from within our Cocoa app,
using NSTask and it crashes, the Cocoa app gets the crash signal
(e.g. return code -11, which is SIGSEGV), but the app does not
write a crash report.
Now, under which circumstances does an application write a crash
report? Or why would it not write a crash report? Is there any
way to influence this programatically? Can I enforce a crashlog
being written? Any ideas? I really need to fix all the bugs in
this application, but I can't, since all I got when it crashes is
"The app has been terminated with exit code -11" (from the Cocoa
app), I can't see which thread crashed or where it crashed. This
is very annoying and really a drawback for our app development.
Just FYI, if the Cocoa app itself crashes, it does write a crash
report, so this has nothing to do with the Cocoa app inheriting
its environment to its child process. Also the daemon calls other
applications from within its context (other system services that
need to run as root using fork/exec) and if these applications
crash, they also leave a crash report.
I'd be eternally grateful if anyone could just give me the
smallest hint where I can at least read something about this
topic. I have not found anything. I ran over all known search
engines, I searched here on the mailing list, I searched the Tech
Notes from Apple, but either I'm not using the right keywords or
there really is nothing about this issue. Please help!
Thank you in advance.
--
Best Regards,
Markus Hanauska
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
40criticalpath.com
This email sent to email@hidden
---
The path of least resistance, it's not just for electricity any more.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden