On 22 Jan 2012, at 18:45, Jens Alfke wrote:
>
> On Jan 22, 2012, at 5:15 AM, Thomas Davie wrote:
>
>> As you can see, none of that is in my code (beyond main), so I have a real
>> problem debugging what's going on here.
>
> Cocoa debugging tip: A crash in objc_msgsend almost always implies a
On Jan 22, 2012, at 5:15 AM, Thomas Davie wrote:
> As you can see, none of that is in my code (beyond main), so I have a real
> problem debugging what's going on here.
Cocoa debugging tip: A crash in objc_msgsend almost always implies a dangling
reference to a deallocated object. Usually the
Thanks Andreas,
I am indeed using ARC, so the code should be safe enough, as ARC will retain
rec for me.
Cheers for taking a look though
Tom Davie
if (*ra4 != 0xffc78948) { return false; }
On 22 Jan 2012, at 13:35, Andreas Grosam wrote:
>
> On Jan 22, 2012, at 2:15 PM, Thomas Davie wrote:
>>
On Jan 22, 2012, at 2:15 PM, Thomas Davie wrote:
>OSPConnection *rec = [[self connectionQueue] objectAtIndex:0];
>[[self connectionQueue] removeObjectAtIndex:0];
>[[self currentConnections] addObject:rec];
Not sure if this is related to your issue, but basical
Hi all,
I'm having a bit of a bizarre issue with a pair of NSXMLParsers reading out of
streams, where my main thread crashes while signalling a stream.
Every crash occurs in the main thread, with this back trace:
> #00x0175d0b0 in objc_msgSend ()
> #10x0133fb4d in _outputStreamCallbackFu
