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.

**************************************************************

"Oleg Starodumov" wrote:
>> 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.
>
>Oleg
>
>
>
>



--
Sent via .NET Newsgroups
http://www.dotnetnewsgroups.com
.

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: An application crashes only under debugging
    ... Oleg Starodumov wrote: ... >>istruction of the DLL attempts to read a memory location which cannot be ... > Here are some differences when an application is running under debugger ... > You can use PageHeap to check the application and the DLL for heap-related problems. ...
    (microsoft.public.vc.language)
  • 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)
Loading