Re: Break points with a "?"


> I am not sure how it is made that way.
> The "another process" is in VB6.0, for GUI. The debugger is attached to
> this process while debugging in two ways:
> 1. Run the target app (VB6.0), come to the VC++ .Net project, go to
> Debug->Process->Attach->"another process"
> 2. Go to VC++ .Net project->Properties->Configuration
> properties->Debugging->Command. Here key in the "another process" name
> and path. (Now F5 would load this "another process")
>
> Either of the ways, the break points dont break. It was breaking before
> a couple of days back.
>

I am not sure that I understand the configuration, but it looks like the DLL
contains a COM component, which is called from VB6 application. Right?
If it is right, the COM component should be an "in-process" COM server,
which therefore should run in the same process with the client (unless it is
configured so that it is hosted in another ("surrogate") process, e.g. dllhost.exe,
and usually it is done using COM+ or DCOM configuration applets).

If you do not make any explicit steps to register the component to run in the
surrogate process, then it should run in the same process with the client.
That is, in the same process with VB6 application. Then the DLL should be visible
in Modules window of the debugger when it is attached to the VB6 application's process
(and if it is not visible there, it means that it is not loaded at all, and you should determine
why it is not loaded).

If you do register the component to run in a surrogate process, the DLL will
be loaded into the surrogate process, and you should attach the debugger
to that process.

You can check which process the DLL is loaded into by e.g. printing the current
process id (GetCurrentProcessId()) to the debug output (e.g. using ATLTRACE)
and watching the debug output with the help of this tool:
http://www.sysinternals.com/Utilities/DebugView.html

Oleg






.

Relevant Pages

  • Re: How to connect to children process
    ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
    (microsoft.public.vsnet.debugging)
  • Re: How to connect to children process
    ... AFAIK that's how VS2003 debugger works, ... unload symbols completely after the dll ... Also, when setting breakpoint on the needed function (in WinDbg), ... I'm creating code with int 3 in place that I'm willing debug. ...
    (microsoft.public.vsnet.debugging)
  • Re: Debugging JNI shared libraries
    ... >compiles OK on Win32 when I have teh requisite stuff installed and I'm ... >DllMain gets called, attach to the dll? ... code as far as the debugger is concerned). ...
    (comp.programming)
  • Re: AD+ crash logs and .dmps Part II
    ... This a .dll provided by an online payment verification ... The Debugger docs have some basic info but overall, understanding ... details the formation and usage of the stack. ...
    (microsoft.public.inetserver.iis.security)
  • Re: How to connect to children process
    ... I'm creating code with int 3 in place that I'm willing debug. ... Then project is rebuild in VS 2003 and target DLL is copied to remote PC ... Thanks to your help I'm able now using WinDbg on local machine. ... I'm not sure if VS debugger provides any API, ...
    (microsoft.public.vsnet.debugging)
Loading