Re: How do decipher an exception in the log file
Re: How do decipher an exception in the log file
- Subject: Re: How do decipher an exception in the log file
- From: Gabriel Zachmann via Cocoa-dev <email@hidden>
- Date: Fri, 21 Jul 2023 16:06:58 +0200
Thanks a lot for the hint.
Alas, the user has reported that Console does not show any crash report w.r.t.
my screensaver.
My guess would be that this is because a .saver bundle, when launched by the
screen saver engine, does not count as a process of its own. Or, at least, the
OS will not store a crash log, if the thread crashes.
Should the user be looking somewhere else?
Best regards, Gabriel
> On 20. Jul 2023, at 10:12, Saagar Jha <email@hidden> wrote:
>
> Console should have it. That crash log will have the base address in it that
> you can use to symbolicate things.
>
> Saagar Jha
>
>> On Jul 18, 2023, at 16:01, Gabriel Zachmann via Cocoa-dev
>> <email@hidden> wrote:
>>
>>
>>> That number is 0x7FFFFFFFFFFFFFFF, which is particularly recognizable and
>>> happens to be the value of NSNotFound.
>>>
>>> I imagine that in the preceding line of code you called -indexOfObject: on
>>> an array that didn't contain the object, but then failed to test the value
>>> against NSNotFound before trying to fetch from that index.
>>>
>>
>> Thanks a million!
>> Very interesting observation.
>> The fact that
>> 9223372036854775807 = 0x7FFFFFFFFFFFFFFF
>> escaped me.
>> And, indeed, I do have a few indexOfObject's in my code, and luckily not
>> that many.
>>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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