• 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: App give s -35 error when run out of the debugger
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: App give s -35 error when run out of the debugger


  • Subject: Re: App give s -35 error when run out of the debugger
  • From: "Jason T. Slack-Moehrle" <email@hidden>
  • Date: Tue, 13 Nov 2012 08:00:37 -0800


Fritz,

> So it seem the paths are like:
>
> .\Flg.h
> .\Dreamsuite\DS1Preferences.iqu
> .\DreamSuite\DS1SecurePreferences.iqu
> .\Dreamsuite\SplashScreen.iqu

[snip] 
 
Backslash is simply not a path separator in UNIX. This is fundamental. Most operating systems are not Windows. If it somehow works, the system is being merciful; don't rely on that mercy's being granted in all cases.

For debugging, Xcode sets the current working directory for an application to the directory into which the application was built. When you run the application on its own, the cwd is the root of the file system (/) for Cocoa applications, and whatever the "pwd" command would print for command-line applications. Relative file paths will therefore resolve to different absolute paths in the debugger and in real life.

In the Run section of the Scheme editor, Options tab, you can set a working directory for Xcode to use for debugging.

The paths you show are relative paths; in effect the path to the current working directory is prepended to them before the app tries to open/create files at those paths. "./" is a synonym for the cwd. Again, that will be different depending on whether you launch from Xcode or from the Finder/command line.


I did amend and say that paths are being passed in as:

.\Flg.h

and being returned as:

./Flg.h

if on OS X. The previous developer seems to be doing this right.

The app is being run from the same place as it is build. The Debugger launches from this same location, no? So it works when run in the debugger, not when run outside like Finder/command-line.

I dont know of a scheme editor in XCode 3.2.6....

Jason
 
 _______________________________________________
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

  • Follow-Ups:
    • Re: App give s -35 error when run out of the debugger
      • From: Jens Alfke <email@hidden>
    • Re: App give s -35 error when run out of the debugger
      • From: Fritz Anderson <email@hidden>
References: 
 >App give s -35 error when run out of the debugger (From: "Jason T. Slack-Moehrle" <email@hidden>)
 >Re: App give s -35 error when run out of the debugger (From: "Jason T. Slack-Moehrle" <email@hidden>)
 >Re: App give s -35 error when run out of the debugger (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: App give s -35 error when run out of the debugger
  • Next by Date: Re: App give s -35 error when run out of the debugger
  • Previous by thread: Re: App give s -35 error when run out of the debugger
  • Next by thread: Re: App give s -35 error when run out of the debugger
  • Index(es):
    • Date
    • Thread