Reputation: 759

Debugging Delphi Application on Non Development Environment

I am attempting to use WinDBG or another debugger to debug a CodeGear Delphi 2007 Windows application on a remote machine. I have been unable to produce symbol files for WinDBG.

Is there a way to use WinDBG or another debugger to debug Delphi applications on a system that doesn't include the IDE?

Edit1

The remote debugger is not an option here. I am able to remote in to the end user PC, but I am unable to use the remote debugger due to firewall restrictions.

Edit2

I am able to remote in to the machine, but can not connect the CodeGear remote debugger due to firewall restrictions.

Upvotes: 9

Answers (7)

Marc Durdin

Reputation: 1803

http://sourceforge.net/projects/tds2dbg/ can be used to convert Delphi's TDS debug files to DBG files. This gives basic symbol information -- functions, classes, units, but not variables. Enough for a reasonable call stack, and with a bit of knowledge, enough to debug Delphi apps live and with dumps.

I've written about some of Delphi+WinDBG experiences on my blog: https://marc.durdin.net/2015/11/windbg-and-delphi-a-collection-of-posts/

Upvotes: 1

Dustin Venegas

Reputation: 759

Thank you all for the great suggestions and interesting products.

To solve this specific issue, the "best" way I found uses the OutputDebugString located in the Windows namespace. This, along with Debug View from Sysinternals, will allow me to gather debug information and sort through it pretty quickly.

If you decide to use this method, make sure everything is wrapped in ANSI formatting. IE:

OutputDebugString(PAnsiChar(string1 + string2));

This makes sure that string1 and string2 are combined and then converted in to ANSI Characters.

I probably should have just started dumping text to a file for something quick and dirty, but this will allow a non-debugging version to emit debugging messages.

Upvotes: 0

onnodb

Reputation: 5273

I'm afraid this is one more of those "I don't have an actual answer" answers, but it might just help...

Have you considered adding logging to your application? I've heard great things about SmartInspect. With it, you can log all sorts of information, including stack traces and "watches" (variables).

Another logging product for Delphi is EurekaLog.

Upvotes: 2

user9977

Reputation: 454

You can try generating a map file and then convert it to a dbg file using map2dbg from http://code.google.com/p/map2dbg/

Then you can load the dbg file in WinDbg.

Disclaimer: I had faced a similar issue but I managed to do remote debugging and didn't have to do all this. So I am not sure this will work. But if you try it then do let us know if it works.

Upvotes: 4