• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSTask prevents crashreporter from running when child process crashes?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTask prevents crashreporter from running when child process crashes?


  • Subject: Re: NSTask prevents crashreporter from running when child process crashes?
  • From: Michael Watson <email@hidden>
  • Date: Tue, 24 Apr 2007 10:11:14 -0400

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:
40bungie.org


This email sent to email@hidden

_______________________________________________

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


  • Follow-Ups:
    • Re: NSTask prevents crashreporter from running when child process crashes?
      • From: Markus Hanauska <email@hidden>
References: 
 >NSTask prevents crashreporter from running when child process crashes? (From: Markus Hanauska <email@hidden>)

  • Prev by Date: Re: Request for Authors: Focused Cocoa Topic Books
  • Next by Date: Re: Any way to find out user's default email client?
  • Previous by thread: NSTask prevents crashreporter from running when child process crashes?
  • Next by thread: Re: NSTask prevents crashreporter from running when child process crashes?
  • Index(es):
    • Date
    • Thread