Re: Can't send messages to a valid object
Re: Can't send messages to a valid object
- Subject: Re: Can't send messages to a valid object
- From: j o a r <email@hidden>
- Date: Sat, 4 Oct 2003 11:20:39 +0200
I would bet good money on that you make a simple retain-release error
somewhere in your code. Use methods described in NSDebug.h (and the
list archives) to track down the problem efficiently, if you cannot do
so by code inspection.
I don't think that you can pose as NSObject and count on being able to
intercept all allocations-deallocations, because not all objects are
decendents of NSObject - some are instances of bridged CF classes, and
they don't use the NS methods.
j o a r
On 2003-10-04, at 04.14, Charles Jolley wrote:
[Please excuse this message if it is a repost; I think the first
message was rejected because it was sent from the wrong address.]
Hi:
I am encountering a very obscure bug in my code that does not seem to
make any sense. The basic issue is that when I send any message to an
object (in code or via command line in GDB) then I get a
EXC_BAD_ACCESS signal inside of objc_msgSend. However, I can inspect
the object's memory and all of its ivars are intact and can be
accessed directly.
The problem occurs sporadically, which made me think that this would
be some kind of memory corruption issue. However, I have posed
NSObject to disable all deallocs, so I know the memory is valid.
Additionally, I can inspect the memory and everything looks to be in
order.
Has anyone seen anything like this before? If not, does anyone have
any suggestions on what I can do to further diagnose this issue?
We have reproduced this bug on Panther 7B68 and 7B74 running on
several different G4 machines (dual, single, and a powerbook.)
_______________________________________________
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.