Re: 0x3ff00000 is what, exactly?
Re: 0x3ff00000 is what, exactly?
- Subject: Re: 0x3ff00000 is what, exactly?
- From: Darrin Cardani <email@hidden>
- Date: Thu, 20 Nov 2003 14:47:37 -0600
At 11:17 AM -0800 11/20/03, email@hidden wrote:
However, while it is not always the same object it crashes on (these
objects represent paths, among other things) the object is always at
address 0x3ff00000. Does this address have some significance? The
debugger shows all the instance vars to be 'invalid', as though there
isn't really an object there, or something.
Any thoughts? Is this some kind of out-of-memory error? Is there a
limit to the number of objects you can instantiate? The number of
NSStrings?
Most likely, you're looking at memory that was recently used for
something else and you've read past the end of an array or something
like that. The value 0x3ff00000 can be just about anything. Here are
some possibilities:
signed chars: 63, -16
unsigned chars: 63, 240
short: 16368
long: 16368
float: 1.875 (or 1 and 7/8ths)
Unicode: "WW"
ASCII: question mark, apple, null, null
Darrin
--
Darrin Cardani - email@hidden
President, Buena Software, Inc.
<
http://www.buena.com/>
Video, Image and Audio Processing Development
_______________________________________________
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.