Re: Error messages
Re: Error messages
- Subject: Re: Error messages
- From: Public Look <email@hidden>
- Date: Sun, 29 Feb 2004 09:31:00 -0500
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 ?
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.