How to troubleshoot an unhandled win32 exception in a Delphi 2010 application?

I'm running Delphi 2010 Professional on an XP Pro machine. I've been working on a program for several days. Each time I run the program on my development machine it runs fine or so I thought. I run the program from within the IDE and it runs fine. I run the program from the output directory (outside the IDE) and it runs fine. I've had no issues anytime I run this program on my machine.

So, to simulate the customer experience, I copied the .exe file onto a memory stick and then copied it to a completely different machine. When I ran the program on that different machine I get an unhandled win32 exception.

Here is the error dialog:

+------------------------------------------------------------------------------+
| Visual Studio Just-In-Time Debugger                                          |
+------------------------------------------------------------------------------+
| An unhandled win32 exception occured in ZilchStd.exe [984]. Just-In-Time     |
| debugging this exception failed with the following error: No installed       |
| debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time  |
| debugging can be enabled from the Tools/Options/Debugging/Just-In-Time.      |
|                                                                              |
| Check the documention index for "just-in-tim debugging, errors' from more    |
| information.                                                                 |
+------------------------------------------------------------------------------+

I've never had this happen to me before. How do I troubleshoot this error?

Upvotes: 1

Views: 1078

Answers (1)

Ken White
Ken White

Reputation: 125620

Use MadExcept, which will allow you to view a stack trace and more infromation about the error. It's free for non-commercial use (meaning testing your app like you did, but not distributing it as part of your app), and a commercial-use license is extremely useful and affordable.

You can even configure MadExcept to email you bug reports from your end users, which can include detailed environmental information like hardware configuration and system library versions.

There are other debugging tools available like the JCLDebug functionality included in Jedi and commercial products like EurekaLog; I've never used either of them, so I can't commment comparitively.

Upvotes: 7

Related Questions