• 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: access violation after using NSTask
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: access violation after using NSTask


  • Subject: Re: access violation after using NSTask
  • From: "James W. Walker" <email@hidden>
  • Date: Fri, 1 Jan 2010 19:07:50 -0800

On Jan 1, 2010, at 6:04 PM, Ken Thomases wrote:

> Try turning off "Auto-attach debugger on crash" in the executable's settings (the "executable" in the sense of Xcode's representation of your app's executable, in its project).
>
> I believe that Xcode may actually be attaching to the child process and not your app.  The auto-attach feature works in a way which can be inherited by child processes.  When one of those crashes, Xcode gets confused and thinks the app it directly launched has crashed.

Bingo!  Many thanks.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >access violation after using NSTask (From: "James W. Walker" <email@hidden>)
 >Re: access violation after using NSTask (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: access violation after using NSTask
  • Next by Date: NS_INLINE and obj = nil;?
  • Previous by thread: Re: access violation after using NSTask
  • Next by thread: NS_INLINE and obj = nil;?
  • Index(es):
    • Date
    • Thread