As part of my JOB, often I have to analyse un-reproducible retail crashes with/ without a core dump. I am generally equipped with
Generally, based on the offset and generating the dis-assembly via objdump, I calculate the failing instruction (machine code/assembly code).
The next JOB is tedious. I try to map the failing instruction to the actual source location. This is time consuming and painful. Is there a painless, easy way to map the source code to the failing instruction?
I tried using the assembly source using the gcc -S option, but cannot effectively map the source. I generally cannot find a logical way to map the assembly output with the crashing offset with the source.
Please suggest the recommended approach.
Create your retail code with debugging information enabled, then strip it before shipping but keep it for yourself. Then you can use your copy for analyzing core dumps.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With