Re: How do decipher an exception in the log file
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 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 >> wrote: >> >> >>> That number is 0x7FFF, 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 = 0x7FFF >> escaped me. >> And, indeed, I do have a few indexOfObject's in my code, and luckily not >> that many. >> smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How do decipher an exception in the log file
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 > wrote: > > >> That number is 0x7FFF, 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 = 0x7FFF > escaped me. > And, indeed, I do have a few indexOfObject's in my code, and luckily not that > many. > > >>> 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. > > Problem is that its a screensaver (i.e., a .saver file). > I guess the base adress is always different, at least I have no idea what the > base address might be. > >> A full-on crash report, rather than log messages, would be a lot more useful. > > Where would i find that crash report, given its a screensaver? > Just in case something like that happens again ... > > > Best regards, Gabriel > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/saagar%40saagarjha.com > > This email sent to saa...@saagarjha.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How do decipher an exception in the log file
> That number is 0x7FFF, 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 = 0x7FFF escaped me. And, indeed, I do have a few indexOfObject's in my code, and luckily not that many. >> 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. Problem is that its a screensaver (i.e., a .saver file). I guess the base adress is always different, at least I have no idea what the base address might be. > A full-on crash report, rather than log messages, would be a lot more useful. Where would i find that crash report, given its a screensaver? Just in case something like that happens again ... Best regards, Gabriel smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How do decipher an exception in the log file
> On Jul 18, 2023, at 9:28 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > 2023-07-17 13:13:23.657278+0200 0xff744Error 0x1144e1 > 2670 0legacyScreenSaver: [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 0x7FFF, 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How do decipher an exception in the log file
Look in the second line. It’s cratering within setLegacyModelView of your view
controller.
Then in the 3rd, it’s saying that the index value of the array is invalid, it’s
9223372036854775807.
So, it’s trying to set the view and the index is clearly the result of a bad
pointer. Gotta run or we could say why.
GL.
> On Jul 18, 2023, at 11:28 AM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> Does anybody know how I could decipher the following entries in the log file?
> More precisely, is there a way I can determine the location in the code where
> the exception occurred?
>
> Thanks a lot in advance.
>
> G.
>
> 2023-07-17 13:13:23.650173+0200 0xff744Default 0x1144e1
> 2670 0legacyScreenSaver: (ScreenSaver) [com.apple.ScreenSaver:Modules]
> -[ScreenSaverView setScreenSaverModule:] -- Setting module “ArtSaver” for
> view: 0x7fe349028000
> 2023-07-17 13:13:23.650194+0200 0xff744Default 0x1144e1
> 2670 0legacyScreenSaver: [com.apple.ScreenSaver:Modules]
> -[LegacyViewController setLegacyModuleView:] -- inView Size: {114, 66}
> 2023-07-17 13:13:23.656894+0200 0xff744Default 0x1144e1
> 2670 0legacyScreenSaver: (ExceptionHandling) NSExceptionHandler has
> recorded the following exception:
> NSRangeException -- *** -[__NSArrayM objectAtIndexedSubscript:]: index
> 9223372036854775807 beyond bounds [0 .. 0]
> Stack trace: 0x7ff80775142b 0x7ff807d053ca 0x7ff807ba19a1 0x1006871a5
> 0x7ff80ac5c3e6 0x7ff80ac65c6c 0x10001a411 0x10001bcc6 0x7ff807ba8377
> 0x7ff807ba820e 0x10001b990 0x7ff807937033 0x7ff807944c60 0x7ff807937033
> 0x7ff807943fcf 0x7ff807943c07 0x7ff807bf3205 0x7ff807bb2f2f
> 0x7ff807bb1f31 0x7ff81162ddad 0x7ff81162dbbe 0x7ff81162d918
> 0x7ff80ac465d0 0x7ff80ac4547a 0x7ff80f981486 0x7ff80f981221
> 0x7ff80f981408 0x7ff80f96ea61 0x7ff80ac37ae8 0x7ff80ac0bd02
> 0x7ff80782a851 0x7ff80782a1f7 0x7ff808a5f58d 0x7ff81549f43b
> 0x7ff81549f03f 0x7ff81549f80a 0x7ffa26eee05f 0x7ff808ac2e54 0x7ff80777e41f
> 2023-07-17 13:13:23.657093+0200 0xff744Error 0x1144e1
> 2670 0legacyScreenSaver: [com.apple.ScreenSaver:Modules]
> -[LegacyExtensionManager exceptionHandler:shouldHandleException:mask:] --
> Module: ArtSaver threw an uncaught exception: NSRangeException, reason: ***
> -[__NSArrayM objectAtIndexedSubscript:]: index 9223372036854775807 beyond
> bounds [0 .. 0].
> 2023-07-17 13:13:23.657278+0200 0xff744Error 0x1144e1
> 2670 0legacyScreenSaver: [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]
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com
>
> This email sent to z...@mac.com
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
