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: Ben Kennedy via Cocoa-dev <email@hidden>
- Date: Tue, 18 Jul 2023 09:58:51 -0700
> On Jul 18, 2023, at 9:28 AM, Gabriel Zachmann via Cocoa-dev
> <email@hidden> wrote:
>
> 2023-07-17 13:13:23.657278+0200 0xff744 Error 0x1144e1
> 2670 0 legacyScreenSaver: [com.apple.ScreenSaver:Modules]
> -[LegacyExtensionManager processExtensionRequest:replyInfo:]_block_invoke --
> Module: ArtSaver (ArtSaver) failed to load. Exception: NSRangeException,
> reason: *** -[__NSArrayM objectAtIndexedSubscript:]: index
> 9223372036854775807 beyond bounds [0 .. 0]
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.
> More precisely, is there a way I can determine the location in the code where
> the exception occurred?
Do you have symbols for the particular build of the app that crashed? If so,
there ought to be some way to symbolicate the list of addresses in the "Stack
trace:" line of the log messages... although maybe not, without knowing the
base load address of the executable. A full-on crash report, rather than log
messages, would be a lot more useful.
-ben
_______________________________________________
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