• 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
starting an app with execve()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

starting an app with execve()


  • Subject: starting an app with execve()
  • From: Devon E Bowen <email@hidden>
  • Date: Wed, 23 Jun 2004 05:44:36 -0400 (EDT)

I am trying to launch a Cocoa app myself via a standard UNIX fork/execve.
I am building a crash detector into my code (to snag seg faults, bus
errors, etc) and when a crash is encountered, I want the code to fork()
and execve() the original executable.

When I try this, the fork/execve seems to work, but I get the following
error after the app relaunches:

2004-06-23 11:37:44.201 MyApp[1546] No Info.plist file in application bundle or no NSPrincipalClass in the Info.plist file, exiting

So apparently, Cocoa requires some state such as an environment variable
or current directory or something that I don't know about. This is, I
guess stopping it from finding the Info.plist file in its bundle. Does
anyone know how to go about doing this or what the above message means?

Devon
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: starting an app with execve()
      • From: Allan Odgaard <email@hidden>
  • Prev by Date: (Command-)Option-Clicking a Window
  • Next by Date: Re: [Newbie] Quitting App automatically
  • Previous by thread: Re: (Command-)Option-Clicking a Window
  • Next by thread: Re: starting an app with execve()
  • Index(es):
    • Date
    • Thread