-
Notifications
You must be signed in to change notification settings - Fork 3k
tools: crash_log_parser: make ELF and MAP parameters optional #7174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tools: crash_log_parser: make ELF and MAP parameters optional #7174
Conversation
On some bug reports the customer is providing only the raw crash dump but not the ELF and MAP files. Those files are needed to decode the addresses into symbol names, but the extremely useful fault reason can still be decoded even without them. By making the ELF and MAP arguments optional, one can now decode the raw dump content into something such as: --8<--8<-- ELF or MAP file missing, logging raw values. Crash Info: Crash location = <unknown-symbol> [0x000091F4] (based on PC value) Caller location = <unknown-symbol> [0x00018E39] (based on LR value) Stack Pointer at the time of crash = [200091E8] Target and Fault Info: Processor Arch: ARM-V7M or above Processor Variant: C24 Forced exception, a fault with configurable priority has been escalated to HardFault The processor has attempted to execute an undefined instruction
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
/morph build |
Build : SUCCESSBuild number : 2321 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1943 |
Test : FAILUREBuild number : 2099 |
We're looking into some CI issues at the moment. The test will be restarted when the dust has settled. |
re-triggering failing tests /morph test |
Test : SUCCESSBuild number : 2144 |
Hello @TeroJaasko @0xc0170 , |
@adustm : point of this PR was not to remove need for MAP completely, but allow decoding at least some of the crash log information in case the ELF & MAP are not available at all. |
Description
On some bug reports the customer is providing only the raw
crash dump but not the ELF and MAP files. Those files are
needed to decode the addresses into symbol names, but the
extremely useful fault reason can still be decoded even
without them.
By making the ELF and MAP arguments optional, one can now
decode the raw dump content into something such as:
--8<--8<--
Pull request type