• 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
0x3ff00000 is what, exactly?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

0x3ff00000 is what, exactly?


  • Subject: 0x3ff00000 is what, exactly?
  • From: email@hidden
  • Date: Thu, 20 Nov 2003 13:27:53 -0500

So, I have this program that creates about 1000 instances of one class. Every now and then it just crashes mysteriously, and debugging shows it to be attempting to send a message to a non-existent object (EXC_BAD_ACCESS).

However, this object exists, as given by the same behavior if I include an
if (obj == nil) return;
before calling the particular method that crashes (always the same one, a method that accesses the NSString that represents the path).

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?

I'll try to make a simple test program to isolate the problem, if I can.

Thanks,
J.D.
_______________________________________________
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.

  • Follow-Ups:
    • Re: 0x3ff00000 is what, exactly?
      • From: "David W. Halliday" <email@hidden>
  • Prev by Date: Dragging out of an NSBrowser
  • Next by Date: Re: writing to a textview
  • Previous by thread: Dragging out of an NSBrowser
  • Next by thread: Re: 0x3ff00000 is what, exactly?
  • Index(es):
    • Date
    • Thread