Discussion:
Remote Just-in-Time Debugging with VS2008?
(too old to reply)
nomad
2008-11-06 10:01:01 UTC
Permalink
I'm trying to debug an MFC application that's being launched by the Shell
under Vista in response to double-clicking a file. I want the debugger to
catch the app in InitInstance(), before it really gets started. But I need to
debug remotely, so I have my debugger set up on another machine, I'm running
the VS Remote Debugging Monitor on the Vista box, and I have a call to
DebugBreak() in the InitInstance() method.

The problem is, I can't figure out how to get the debugger to automatically
connect to the app on the other side of the connection. There doesn't appear
to be any 'wait for process' setting that I can apply to a remote target. Or
is there?

How does one do this?
David Lowndes
2008-11-06 11:43:04 UTC
Permalink
Post by nomad
I'm trying to debug an MFC application that's being launched by the Shell
under Vista in response to double-clicking a file. I want the debugger to
catch the app in InitInstance(), before it really gets started. But I need to
debug remotely, so I have my debugger set up on another machine, I'm running
the VS Remote Debugging Monitor on the Vista box, and I have a call to
DebugBreak() in the InitInstance() method.
The problem is, I can't figure out how to get the debugger to automatically
connect to the app on the other side of the connection. There doesn't appear
to be any 'wait for process' setting that I can apply to a remote target. Or
is there?
I'm not aware of how to do it either.
In your situation I'd just put a temporary messagebox call in so the
application will halt while you attach to the process.

Dave
nomad
2008-11-06 13:54:01 UTC
Permalink
Post by David Lowndes
In your situation I'd just put a temporary messagebox call in so the
application will halt while you attach to the process.
Oh, hey, that's a great idea. Should've thought of that myself. Thanks!
Loading...