Re: Crash on SIGILL

Another really good thing to do is to run the static analyzer in Xcode, and pay attention to whatever warnings it emits. Joar > On 21 nov 2014, at 19:05, Laurent Daudelin wrote: > > Thank you, all, I’m going to turn on GuardMalloc, Zombies and the likes. > > -Laurent. > -- > Laurent Daudel

Re: Crash on SIGILL

Thank you, all, I’m going to turn on GuardMalloc, Zombies and the likes. -Laurent. -- Laurent Daudelin laur...@nemesys-soft.com AIM/iChat/Skype:LaurentDaudelin http://www.nem

Re: Crash on SIGILL

Two messages in one day with the exact same crash report in them - with the same memory locations in the crash report even. That seems beyond unlikely - is this actually one crash report where the original user happened to post it here as well as reporting it, or there really are two. I reco

Re: Crash on SIGILL

> On Nov 21, 2014, at 9:24 AM, Laurent Daudelin > wrote: > > Just got a crash report from a user. There is nothing in the trace that > relates to my app. The application specific information shows: > > Application Specific Information: > objc[60867]: Method cache corrupted. This may be a messa

Re: Crash on SIGILL

> On Nov 21, 2014, at 9:24 AM, Laurent Daudelin > wrote: > > I've never seen this. Anybody has any clue what could cause a method cache > corrupted? Well, general heap corruption, I suppose, like overwriting the end of a block or writing to previously-freed memory. These kinds of problems a

Crash on SIGILL

Just got a crash report from a user. There is nothing in the trace that relates to my app. The application specific information shows: Application Specific Information: objc[60867]: Method cache corrupted. This may be a message to an invalid object, or a memory error somewhere else. objc[60867]: r