Re: How to connect to children process


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




.

Relevant Pages

  • Re: Debugging Tools for Windows - WinDbg
    ... I am going to look into WinDbg because I often faced the needs debugging crash dumps. ... VS debugger is targeted towards better usability and productivity when performing ...
    (microsoft.public.vc.mfc)
  • Re: Wininet PORT command
    ... But even with knowledge of the source code I ... time trying to debug it. ... It's possible to debug an app with WinDbg using symbols for MS DLLs (that ... Debugging will most likely be in assembly language (I'm not ...
    (microsoft.public.win32.programmer.networks)
  • Re: Memory Leak
    ... Scan Thread 0 OSTHread 1490 ... SOS.dll which is written by the CLR team for internal debugging purpose. ... we need to install windbg to debug this memory leak instead of using ...
    (microsoft.public.dotnet.languages.csharp)
  • Windbg hangs while debugging XPe BSOD
    ... But, recently we've seen BSOD ... We have a headless, EWF-enabled Compact Flash system. ... enable debugging and set windbg on the serial port. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Memory Leak
    ... SOS.dll which is written by the CLR team for internal debugging purpose. ... we need to install windbg to debug this memory leak instead of using VS ... You can send feedback directly to my manager at: ...
    (microsoft.public.dotnet.languages.csharp)
Loading