Again Unix to the rescue. http://stackoverflow.com/questions/19147386/system-call-fork-and-execv-function
Sent from my iPhone On 2015/03/10, at 18:08, Torsten Curdt <tcu...@vafer.org> wrote: >> >> However the user experience is rather barren. >> The app simply dies. > > >> As well as posting the report ReportCrash(8) also allows informs the user >> of termination and allows restart. >> I know that prompting users twice for reporting is inelegant and confusing >> but crashing with no UI feedback at all is a bit mystifying - where did my >> app go! > > > True. It would be better to have a custom dialog - but from a signal > handler? > > > Throwing up any sort of UI in the callback will be unreliable due to the >> normal re-entrant code caveats - I think the Adium code does this anyway. > > Where did you find that? > > Well, I guess a crash is a crash. So maybe unreliable ist acceptable if it > works most of the time. After all a crash *should* be an edge case that > does not happen too often. > > Maybe this could be done from another process? > > cheers, > Torsten > _______________________________________________ > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com > > This email sent to dangerwillrobinsondan...@gmail.com _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
