Re: How to connect to children process

Oleg,

Local debug is not always suitable. Therefore we would like to find more
general solution.

Other manual operations are:
(a) Re-starting of process A under WinDbg
(b) Reload symbols at first break (.reload /user)
(c) Restoring of break points (or embedding of DebugBreak(s))

Al




"Oleg Starodumov" wrote:


The problem of locked pdb should not exist in the local scenario
(when debugging the parent process (A) and its children with WinDbg
on the local machine).

What other manual operations are needed at this time (in local scenario)?
(other than recompiling the dll and (optionally) copying the new version
over the old one?)

Oleg

Oleg,

Main problem is amount of manual operations required per debug cycle.
Locking of symbols is only part of this problem.

When I recompile, linker complains that .PDB file cannot be written. For
solve this, I break to WinDbg and invoke .reload /user. After it linker works.

But as I said - loking is only part of the problem. Another part is that
connection to DLL with debugger takes sensible amount of time and manual
operations.

Therefore I'm looking for a method to automate entire procedure.

With best regards,

Al





.

Loading