Windows Debug crash handler

Question

What I'd like to know is if the book "Inside Windows Debugging", published in 2012, has any information about writing crash handlers (with sample code), in particular to get a stack trace. I am most interested in the parameters for StackWalk64 For some reason the stack trace we get doesn't match up with functions that caused the crash. I.e., mapping addresses from our crash log to functions, when we open the executable in windbg and point the symbol search path to the PDBs we have for our product. The product in this case is the shipping product, which doesn't contain the PDB files. We get the stack trace from the shipping product, use windb to open that releases executable, point the PDB search path to where we have tucked away the PDB files we need, and then do the address to function mapping, which gives incorrect information. I am use dbghelp, not imagehlp.

Thanks,

Tom

Answer 1

Hi Tom,

Our forum is related to VS debugger, so the windbg is beyond our support. We suggest you could redirect to stack overflow with windbg tag, and then the community members will provide dedicated support for you.

Thank you for understanding.

Best Regards,
Dylan

------------

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.