How to trace back hard fault handler

[danbujak]

What's the proper way to debug what's causing my eval board to reset? I'm assuming I need to put a breakpoint in the hard fault handle, but how do I trace that back to the source of the error? Or should I modify the handler?

I also noticed that the breakpoint in the hardfault handler isn't triggered unless I step through the code line-by-line. Is this expected?

[Susheel Nuguru]

set the breakpoint little later in the function where error_code is assigned to a global variable. At that point debugger should have known its info.

[danbujak]

That appears to work. What do you do when the local variable isn't assigned to anything?

[Susheel Nuguru]

the compiler is tricky in the way it generates debug info, if you really want to make sure that compiler must at all times produce debug info for some variable, then temporarily declare it volatile while debugging. if this solved your problem then please accept this answer.