Posted on October 28, 2014 at 18:13However, you MUST enable the generation of the map file, and save it for each release build. Analysing the stack/raw memory will only mean something if you can identify the function addresses - this is where you need the map file!
Well technically a .AXF(.ELF) with debug information will actually contain the code and all the salient details, source line mapping, etc. The .MAP would be helpful for human readable output, or parsing with AWK or PERL, etc.
Most of the static analysis tools I'm familiar with are privately held.
In a relatively crude fashion one could simply traverse the stack and associate 32-bit words with addresses of variables, or functions, or offsets/lines within functions.
Hard faults tend to be pretty gross in nature, knowing which line faulted, and the subroutine call immediately above it is usually sufficient to pin point the failure, or add some more guarding on parameters to catch the offending call that created the fault. ie testing for NULL pointers, or array index boundaries.
