0

I develop unmanaged C++ applications in MSVC2008. And occasionally the application crashes at the customer site. I found an article on this. But it was written in 2002 for Visual Studio .NET. Has things changed since? Can the same technique be used? Is there a newer method?

sep
  • 3,409
  • 4
  • 29
  • 32
  • I wish to know if the sample code at the site is still applicable. – sep Aug 28 '10 at 04:58
  • I can deploy debug versions at the customer site. I keep the PDB files. My main question is whether there is still a need to write code to handle exceptions to generate a minidump and whether the provided code is still relevant in the context of MSVC2008 and modern Windows such as Windows 7, Vista, Server 2008. – sep Aug 28 '10 at 05:11

2 Answers2

1

If you are debugging C and C++ apps for Windows, you want to learn how to use WinDBG (distributed as "debugging tools for Windows"). It has a bit of a learning curve, but the documentation is really good and it really is the best the platform has to offer.

As to your question, you can view a crash dump with windbg -z <dump filename>.

asveikau
  • 39,039
  • 2
  • 53
  • 68
0

Usually release mode binaries (which typically run at customer site) are built with optimization (for speed/memory etc). Troubleshooting optimized binaries is usually not as easy.

So, first check if the crash is reproducible with release mode binaries built without optimization. If yes, then the job is easy (ier).

Here is some info.

Also look at a tool called ADPlus from microsoft

Community
  • 1
  • 1
Chubsdad
  • 24,777
  • 4
  • 73
  • 129