Re: Crash on SIGILL
Re: Crash on SIGILL
- Subject: Re: Crash on SIGILL
- From: Joar Wingfors <email@hidden>
- Date: Sat, 22 Nov 2014 10:00:46 -0800
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 <email@hidden> wrote:
>
> Thank you, all, I’m going to turn on GuardMalloc, Zombies and the likes.
>
> -Laurent.
> --
> Laurent Daudelin email@hidden <mailto:email@hidden>
> AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/ <http://www.nemesys-soft.com/>
> Logiciels Nemesys Software
>
>> On Nov 21, 2014, at 19:10, Roland King <email@hidden> wrote:
>>
>> 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 recommended GuardMalloc and Zombies for the first instance.
>>
>>> On 22 Nov 2014, at 6:38 am, Greg Parker <email@hidden <mailto:email@hidden>> wrote:
>>>
>>>>
>>>> On Nov 21, 2014, at 9:24 AM, Laurent Daudelin <email@hidden <mailto:email@hidden>> 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 message to an invalid
>>>> object, or a memory error somewhere else.
>>>> objc[60867]: receiver 0x7ffe16d5b380, SEL 0x7fff8899a0b0, isa
>>>> 0x7fff785f7590, cache 0x7fff785f75a0, buckets 0x7fff9199b465, mask 0x17,
>>>> occupied 0x0
>>>> objc[60867]: receiver 32 bytes, buckets 0 bytes
>>>> objc[60867]: selector 'retain'
>>>> objc[60867]: isa ''
>>>> objc[60867]: Method cache corrupted.
>>>>
>>>> I've never seen this. Anybody has any clue what could cause a method cache
>>>> corrupted? I haven't got any report from anyone else but that user.
>>>>
>>>> Any info, pointer or help appreciated!
>>>
>>> Like the log says: either a message to an invalid object, or a memory error somewhere else that trampled on your valid object or its class's data structures. You should debug it as if it were a crash in objc_msgSend().
>>>
>>>
>>> --
>>> Greg Parker email@hidden <mailto:email@hidden> Runtime Wrangler
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> Cocoa-dev mailing list (email@hidden <mailto:email@hidden>)
>>>
>>> Please do not post admin requests or moderator comments to the list.
>>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com <http://lists.apple.com/>
>>>
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden <mailto:email@hidden>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden