• 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: debug problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: debug problem


  • Subject: Re: debug problem
  • From: Eric Ocean <email@hidden>
  • Date: Sat, 9 Oct 2004 15:39:34 -0700

On Oct 9, 2004, at 3:20 PM, Jacob Lukas wrote:

Could XCode have the file open and auto save it? It doesn't make sense, but you might want to consider it.

It's not open in Xcode to my knowledge, but I am very curious if open file descriptors have something to do with it (though that doesn't explain executing random code). I've heard rumors that Cocoa classes don't always clean up file descriptors like they're supposed to, though I haven't experienced that myself.

On Oct 9, 2004, at 3:24 PM, Agent M wrote:

Have you tried some simpler methods? NSDictionary can read and write plists without any additional work:
- (id)initWithContentsOfFile:(NSString *)path
- (BOOL)writeToFile:(NSString *)path atomically:(BOOL)flag

I'm just wondering if unnecessary complication means you're overlooking something. Xcode doesn't execute your code unless you ask it to.

I use writeToFile: to write it, but (out of habit) I used the other code. It has the advantage of giving a useful error message. Anyway, I modified the code to use -initWithContentsOfFile: same result.

------

Am I the only guy who has stuff like this happen, or is this common with other developers? Honestly, I crank out 200-300 LoQC in a 6 hour day (that works), and then I hit a random bug like this and productivity drops to zero for hours and days on end. I've really developed a distaste for third-party code and developer tools because of it, and yet I realize how much they do help when they work right. Arrrggg.

Anyway, keep the ideas coming. I'll try anything. Does anyone know how to put a breakpoint on the "start" assembler label, or even just a specific location in my executable? Then I could debug from the start: label and see what happens.

Regards,

Eric Ocean
 _______________________________________________
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: 
 >debug problem (From: Eric Ocean <email@hidden>)

  • Prev by Date: debug problem
  • Next by Date: Re: debug problem
  • Previous by thread: debug problem
  • Next by thread: Re: debug problem
  • Index(es):
    • Date
    • Thread