But the issue isn't about parsing log semantics...
It's that a production device entered a state where normally fused-off debug logic became accessible. That shouldn’t be possible, regardless of how the logs were captured or named.
It's that a production device entered a state where normally fused-off debug logic became accessible. That shouldn’t be possible, regardless of how the logs were captured or named.