2005-12-13 20:17:02 UTC
I am very new to using ADPLUS and WinDbg, so I am hoping for several
I have a console app (multithreaded) which is started by a *.cmd file that
is coded to restart if program goes down as we are 24x7, etc. The program
has logic to error & alert operations if it was in the middle of processing.
Both issues are intermittent, though frequent, i.e. weekly or daily.
The first issue is that the program goes down cleanly (no AVs or Dr Watson
dumps). Through conventional logging, I am getting close to where it is
going down (thread #s are part of log).
The second issue is where we read a record in from disk, do a db lookup (via
ODBC) based on the variables retrieved from the file's record. When the db
lookup is done, the program errors that it cannot find the db record because
the variables (which were pop. by the file's record) are blank.
Can WinDbg be used to debug these types of scenarios on a "live" program -
w/out interfering with the program? If so, how? What information would I be
Would I use ADPLUS with some sort of break points to create a dump file? If
Any and all ideas would be appreciated.