Re: trouble debugging a DLL in VS2005

Tech-Archive recommends: Fix windows errors by optimizing your registry




I have a project (lets call it proj1) that includes a DLL (say dllA) and
that DLL includes another DLL (say dllB). (btw, both DLLs are user created
DLLs that I created). I'm having a problem debugging dllA. When I step
into the call from proj1 into dllA, it immediately steps into dllB (which is
a call somewhere in the middle of dllA). I can't figure out why dllA is not
being allowed to be stepped through and dllB is. Both dllA and dllB
(although in separate projects) seemed to have been set up in the same
manner and have the same compile options, but apparently there's some
setting that's not allowing me to debug dllA.

Anybody recognize what may be the problem here?



Is it managed application? If so, it is possible that dllA is loaded from
a wrong location, does not have symbols, or is optimized.

You can check for all these things in Modules window - in addition to the
module path, see the following columns:
Symbol Status
Optimized
User Code

What will be shown in these columns for dllA?

Regards,
Oleg
[VC++ MVP http://www.debuginfo.com/]





.



Relevant Pages

  • Program does now invoke methods of ActiveX-DLL
    ... >> declared in that dll. ... > If you have a dll called DLLA and another called DLLB, ... > reference DLLB if DLLB doesn't contain a reference to DLLA... ...
    (microsoft.public.vb.com)
  • trouble debugging a DLL in VS2005
    ... that DLL includes another DLL (say dllB). ... I'm having a problem debugging dllA. ... into the call from proj1 into dllA, it immediately steps into dllB (which is ...
    (microsoft.public.vsnet.debugging)
  • trouble debugging a DLL
    ... that DLL includes another DLL (say dllB). ... I'm having a problem debugging dllA. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: VB6 compilation issue with UDTs and projects in a group
    ... For example, if DLLa needs DLLb, be sure DLLb shows up before ... DLLa so DLLb is built before DLLa.. ... is the last in the list (because the others should be built first) ... I still say groups are for debugging only ...
    (microsoft.public.vb.bugs)
  • is declared in project , which is not referenced by project
    ... Note: DLLB references DLLA. ... remove and readd the reference to DLLA. ... If I reference the projects for DLLA and DLLB instead of the DLLs, ...
    (microsoft.public.dotnet.general)