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
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
> 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
> 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
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
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 0
