> The DLL is made "out of process" and the path of the traget application
> in VB6.0 is correct.
How exactly was the DLL made "out of process"?
> When F5 is pressed, the target application comes
> up, but the modules window in "Debug" menu lists the target application
> (and not the DLL under that needs to be debug).
If the DLL is hosted in another process, you should attach the debugger to that another
process. Or start the process that hosts the DLL (but not the client VB6 app)
under debugger.
Re: Access violation in MSXML.dll ??? ... Are you building your DLL with fully debug or with retail? ... the code gets executed just enough for the debugger to be able to figure out ... Below is the destructor for XML module:... (microsoft.public.windowsce.embedded)
Re: no symbols have been loaded for dll ... The dll is called by non msvc application, ...debug | attach to process and select my application. ... In order for the debugger to associate source file lines to actual machine ... the debugger finds the incorrect .pdb file.... (microsoft.public.vc.ide_general)
Re: Need help troubleshooting perfmon extension dll ... same code into a 32-bit dll, and install it on a 32-bit OS (XP, to begin ... The debug output... Shouldn't the debugger get the first chance,... (microsoft.public.win32.programmer.kernel)
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)
