On Jan 14, 2009, at 11:04 AM, John Nairn wrote:
I occasionally get difficult-to-debug crashes where that last thing
in the crash log is a message being sent, which ends up being a
message sent to an object that has been released (I think it is
objc_msg, but I am not looking at a crash log
On Jan 14, 2009, at 4:21 PM, Sean McBride wrote:
Not to hijack this thread, but... anyone know what objc_msgSend_fixup
is? Recently I've seen a lot of these types of crashes in my
(64bit, GC) app.
I could have sworn I've seen this before, and the problem ended up
being a subtle memory c
On 1/14/09 2:33 PM, Greg Parker said:
>On Jan 14, 2009, at 11:18 AM, Jeff Johnson wrote:
>> On Jan 14, 2009, at 1:04 PM, John Nairn wrote:
>>> I occasionally get difficult-to-debug crashes where that last thing
>>> in the crash log is a message being sent, which ends up being a
>>> message sent to
On Jan 14, 2009, at 11:18 AM, Jeff Johnson wrote:
On Jan 14, 2009, at 1:04 PM, John Nairn wrote:
I occasionally get difficult-to-debug crashes where that last thing
in the crash log is a message being sent, which ends up being a
message sent to an object that has been released (I think it is
John,
See the following for a good tutorial:
http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashed_in_objc_msgSend.html
-Jeff
On Jan 14, 2009, at 1:04 PM, John Nairn wrote:
I occasionally get difficult-to-debug crashes where that last thing
in the crash log is a
I occasionally get difficult-to-debug crashes where that last thing in
the crash log is a message being sent, which ends up being a message
sent to an object that has been released (I think it is objc_msg, but
I am not looking at a crash log now). These happen much more often in
Leopard tha
