6 Commits (afc0a28cc50223436b08f18a29b64f08b9154f8a)

Author	SHA1	Message	Date
Tero Jääskö	274c3fa690	tools: crash_log_parser: make ELF and MAP parameters optional ... 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	2018-06-08 13:32:37 +03:00
Brendan McDonnell	c4f10aafee	typos	2018-02-20 20:11:19 -05:00
Senthil Ramakrishnan	3340a020ed	Fix code style issues and update documentation	2018-02-12 11:50:34 -06:00
Senthil Ramakrishnan	8967b52bfb	crash_log_parser review comment fixes	2018-02-12 11:50:33 -06:00
Senthil Ramakrishnan	96d900c99f	Fixes for targets with invalid HardFault_Handler implementation and review/other fixes	2018-02-12 11:50:33 -06:00
Senthil Ramakrishnan	29348d823d	Support for generating core/register/thread-info dump on fault exceptions	2018-02-12 11:50:33 -06:00