Re: Break points with a "?"


> You are right on the configuration.
> The surrogate one which is hosted by dllhost.exe. We are using regsvcs
> to register and make a .tlb out of it which will be referenced by the
> traget app (in VB6.0).
>
> 1. I could not try with ATLTRACE, it was giving compile errors. I
> included Atlcom.h,Atlbase.h,AtlTrace.h and said "Dynamically link to
> ATL" in project properties but that did not help. It was throwing up
> many ambiguity errors in the above headers
> (TYPEDESC,IDLDESC,PARAMDESC,TYPEKIND,etc,...)
>

You can try using OutputDebugString function directly.

> 2. I tried attaching the dll to both dllhost.exe and also
> targetApp.exe(this is in VB6.0). But it wont break at the inserted
> break-points and "?" yet appears.
>

You should attach to dllhost.exe to debug the DLL.

> 3. Tried attaching the dll to only dllhost.exe, in this case, in the
> Debug->Module window, it shows that the "this.dll" has loaded the
> symbols info and points to the GlobalAssemblyCache where it has been
> loaded. But yet it wont break at the inserted break-points and "?" still
> appears.
>

So it looks like the DLL is managed?

Try these things:

- When attaching the debugger to dllhost.exe process, make sure that you select
both "Native" and "Common Language Runtime" debug engines (in Attach to Process dialog).

- After you have rebuilt the DLL, copy its .PDB file to the same directory where the DLL
is located (to the GAC). (This step is optional and not necessary if the first step helps)

Oleg





.

Relevant Pages

  • Re: Where did my VB function go?
    ... but I also wondered about the virtual memory space ... To clearify I'm creating a DLL ... global data in a DLL is not coherent between all attaching processes, ... shared memory area between all the processes which are attached to my ...
    (microsoft.public.vb.winapi)
  • Re: Cant debug Forms DLL (Managed C++)
    ... and with the other dll I needed to add that dll to the toolbox ... > when I put the debugger to managed only. ... > stands two times in the list, one time with a red exclamation mark. ... >> are attaching, the code must be compiled debuggable. ...
    (microsoft.public.vsnet.debugging)
  • Re: Mutex question
    ... leave something which I can later look for by name and which I'll find if my DLL ... attaching a GUID to a name you can recognize would not be unreasonable ... Doug Harrison ...
    (microsoft.public.vc.language)
  • Re: VB Dll
    ... There are some topics in MSDN there. ... Here I'm attaching a modifed version of a artcle I found on net talked about ... Be sure to watch for the DLL name I used, ...
    (microsoft.public.vc.language)
  • Re: Use .NET DLL from VB6 app -> broken references on rebuild?
    ... "VB developers are urged to set version numbers EXplicitly" ... then recompiling (generating a new tlb file) and seeing if the ... > changing the interface) and just copy the new dll to the second location ... > changing the dll's interface then using the same tlb should be working... ...
    (microsoft.public.dotnet.faqs)
Loading