• 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: EXC_BAD_ACCESS when running from different drive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EXC_BAD_ACCESS when running from different drive


  • Subject: Re: EXC_BAD_ACCESS when running from different drive
  • From: Stefan Werner <email@hidden>
  • Date: Tue, 27 Sep 2005 18:38:17 -0700


On Sep 27, 2005, at 3:05 PM, Daniel Hazelbaker wrote:

What is the call stack up to the crash? Anything to do with filenames or paths in there? Perhaps something to do with the path name(s) is making it crash or not crash.

The call stack would be very meaningless to you, it's basically the constructors of the application's main classes. I did look out for path name issues, nothing that I could tell there. Guard Malloc didn't report any memory problems either.


Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >EXC_BAD_ACCESS when running from different drive (From: Stefan Werner <email@hidden>)
 >Re: EXC_BAD_ACCESS when running from different drive (From: Daniel Hazelbaker <email@hidden>)

  • Prev by Date: Re: C with C++ in xcode
  • Next by Date: Re: Using AppleScript to access a Copy File Phase in an Xcode project
  • Previous by thread: Re: EXC_BAD_ACCESS when running from different drive
  • Next by thread: Re: EXC_BAD_ACCESS when running from different drive
  • Index(es):
    • Date
    • Thread