6/20/2023 0 Comments Tag debugging tools for windows![]() Get the faulting module and offset from the event log Crashy.cpp : Defines the exported functions for the DLL application. If you run this code, then your program will crash with an access violation. Let’s illustrate this with an example that uses a DLL with a single function that deliberately dereferences a null pointer. ![]() Plug these two pieces of information into WinDbg to find the offending line.Get the name of the faulting module and the fault offset from the event log.The Techniqueįortunately, if you’re able to get access to the Windows event logs from the machine, then there are still some steps that you can take to narrow down the problem. For example, it might be a customer’s machine, or it could be a fault that occurs so infrequently that it could be weeks before you see it again. Similarly, if the machine is yours to play with, and the fault is easy to reproduce then you could just enable crash dumps, but this isn’t always an option. If you’d had a minidump then you could have just loaded it into Visual Studio and continued from there. ![]() If you’ve ever been in the frustrating situation of having a crash report from a machine where crash dumps are not enabled, then you’ve probably been left scratching your head wondering what to do.
0 Comments
Leave a Reply. |