Log Parsing Failure

[sammarcus]

Hello 👋

The failure reason for a recent import was:

index out of bounds: the len is 7 but the index is 7
0:_mh_execute_header
1: _mh_execute_header
2: _mh_execute_header
3:_mh_execute_header
4:_mh_execute_header
5: mh_execute_header
6:_isPlatformVersionAtLeast
7:_isPlatformVersionAtLeast
8:_mh_execute_header
9:mh_execute_header
10: _mh_execute_header
11: mh_execute_header
12: _mh_execute_header
13: _mh_execute_header
14: _mh_execute_header
15: _mh_execute_header
16: _mh_execute_header
17: <unknown>
18: <unknown>
19: <unknown>
20: <unknown>
21: <unknown>

this of course isn't helpful without the actual sysdiagnose, so also sharing that over email as well. only ever seen this once, so, super rare, but reproducible every time with this same file. modem firmware 1.55.04 on iPhone 17 Pro iOS 26.4

my suspicion is it could be related to some additional debugging profiles I'd also newly added this week, but evidence against that being related is even when these profile are active I can't reproduce beyond this single occasion. am going to keep trying to pin down what about this sysdiagnose that might be the issue!

[sammarcus]

actually, think this is rooted in the mandiant dependency. looking into opening an issue and exploring fixing it upstream, but also open to ideas of what could be done in interim!

[lukbukkit]

Thanks for the crash report! It's not unusual that some minor changes to Apple's proprietary log archive format break the related Rust Library from Mandiant we're using to parse the log entries.

The latest build of CellGuard includes version 0.4.2 of the library. In February, there were some updates to the library, which could include a fix for your issue. I'll make sure to update the library in the next build.

Feel free to share the sysdiagnose with us for further investigation. Currently, I'm on vacation, but starting in May, I have more time to investigate and fix the issue (and to work on CellGuard in general).

[charminultra-tp]

Hello,

I’ve been using CellGuard for about a week and almost all of my sysdiagnose imports have this error. I’m new to this platform and would like to contribute.

My device:
Apple iPhone 17 Pro Max
MFXG4LL/A
iOS 26.5
Train: iOS 26 Developer Beta
Lockdown Mode Enabled

App:
CellGuard v1.6.0 (8)
Git Commit: 9c9dd57

https://imgur.com/a/9qoBsMK

Thanks for the crash report! It's not unusual that some minor changes to Apple's proprietary log archive format break the related Rust Library from Mandiant we're using to parse the log entries.

The latest build of CellGuard includes version 0.4.2 of the library. In February, there were some updates to the library, which could include a fix for your issue. I'll make sure to update the library in the next build.

Feel free to share the sysdiagnose with us for further investigation. Currently, I'm on vacation, but starting in May, I have more time to investigate and fix the issue (and to work on CellGuard in general).

[lukbukkit]

Hi @charminultra-tp. Thanks for contributing. The warning you've encountered appears as there are some differences between our two parser implementations that collect data about cells you've connected to. This is nothing you have to worry about, but provides interesting technical insight for us.

If you want, you can upload the sysdiagnose file to a cloud provider of your choice and send us a link via e-mail. However, please keep in mind that this file might contain various personal data points.

If I'm not mistaken, the initial post of this discussion referred to another problem. But that's no problem, we'll create two separate issues in our internal bug tracker.