Recommend a debugger
- From: Susan Rice <srice1@xxxxxxx>
- Date: Sat, 03 Feb 2007 13:14:56 -0800
I have only the executables, a .exe file and a .dll file. The program
(.exe) eventually makes a call to a very short routine in the .dll file,
and bombs. I looked at the .dll routine being called with PE Explorer
(http://www.heaventools.com/) and the routine being called is only about
a page long.
Somehow I got to get in there with a debugger to see why it's going
wrong. I have "Debugging Tools for Windows" which has WinDbg.exe,
and "logger.exe" looked promising, but I can't figure out how to
use them.
So is there any decent documentation on how to use WinDbg, or is
there a third party debugger anyone would recommend?
.
- Follow-Ups:
- Re: Recommend a debugger
- From: Susan Rice
- Re: Recommend a debugger
- From: Susan Rice
- Re: Recommend a debugger
- From: Check Abdoul
- Re: Recommend a debugger
- From: David Ching
- Re: Recommend a debugger
- From: Joseph M . Newcomer
- Re: Recommend a debugger
- Prev by Date: Re: MFC, Threads, PostMessage, and Reentrant WindowProc
- Next by Date: Re: CFont Guidance
- Previous by thread: double is integer?
- Next by thread: Re: Recommend a debugger
- Index(es):
Relevant Pages
|
Loading