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

Re: Error messages


  • Subject: Re: Error messages
  • From: April Gendill <email@hidden>
  • Date: Sun, 29 Feb 2004 09:43:43 -0700

On Feb 29, 2004, at 7:31 AM, Public Look wrote:

One difference between "normal" build and debugging is the current working directory when the applications starts. Applications should never rely on the current working directory having any particular value when the application starts. If for example, you are creating relative paths in your application, that could be the problem.

Regarding -setObject:forKey: Just because you don't call it explicitly does not mean it is not called within the frameworks in order to do something. You ran in the debugger, so what was the stack trace. Who called -setObject:forKey: with a nil object or a nil key ?

Well thats just it. No error ever occurred so I could not determine where it was called from. I'm starting to think that this could be a memory issue. This is not the first error I've run into that "migrated" or simply just happened and nothing I could do would trace it.



On Feb 28, 2004, at 9:03 PM, April Gendill wrote:

Ok...
I am working on an application that copies files from point a to point b. When I run the application normally, it fails about half way through no matter what you copy. A big folder a small app basically it just fails. But if I run it through the debugger it works fine. Now the failure message is NSFDictionary setObject:forKey: attempt to insert null value...
There is only one place that insert a value in a dictionary and it has nothing to do with this method, but the value is set using constants not variables. in other words the value is @"YES" and is inserted that way.
There are a few places that Use NSDictionary * tmpDict = [curDict objectForKey:curKey];

Anyway... Any ideas as to why I might be having the error in a normal build and run but not in the debugger?

April.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Error messages (From: April Gendill <email@hidden>)
 >Re: Error messages (From: Public Look <email@hidden>)

  • Prev by Date: Re: Databasing and Cocoa
  • Next by Date: Cursor attribute won't save
  • Previous by thread: Re: Error messages
  • Next by thread: Re: Error messages
  • Index(es):
    • Date
    • Thread