Debugging Unmanaged Library From Managed Library

[Howard Swope]

I have a series of third party libraries for which we have licensed the
source code. These are unmanaged libraries written in C++ which I am able to
build without any trouble. I am trying to setup my environment so that I can
step into their code form my managed .dll written in managed C++ (.Net 1.1).
I just can't seem to get my code to step into their source file.

What Am I missing? What files are required to make this happen? Is there a
certain directory structure they need to maintain to locate a source file?
Etc?

Thanks,

 

[David Lowndes]

I have a series of third party libraries for which we have licensed the

source code. These are unmanaged libraries written in C++ which I am able to
build without any trouble. I am trying to setup my environment so that I can
step into their code form my managed .dll written in managed C++ (.Net 1.1).
I just can't seem to get my code to step into their source file.

What Am I missing?

There's a setting on the project debugger settings to allow mixed mode
debugging.

Dave

 

[Bruno van Dooren]

I have a series of third party libraries for which we have licensed the

There's a setting on the project debugger settings to allow mixed mode
debugging.

You also need to make sure that the source files match the debug build of
your unmanaged libraries.
I have noticed that if I changed a source file after a build, then the
debugger won't break on the breakpoints in the unmanaged sources. This makes
sense of course, but it is one of the pitfalls that I once fell into.

 

[John]

I have the same situation that I can't step into the unmanaged lib
code. The project debuger/mixed setting didn't have any effect on
this (I tried it instead of the default auto).
In my case I have 4 libs (unmanaged) compiled using a separate
solution and linked as static libs into the current solution (all
using vc++ 8 with clr support). Somehow I can only step into one of
the libs, but not the other three.
I noticed all VC projects using vc80.pdb by default. Could this be the
issue? Appreciate if anyone can shed some lights on this.
Thanks
zz

 

[John]

There's a setting on the project debugger settings to allow mixed mode
debugging.

The default is auto that should take care of this (I also tried mixed,
no difference). I've the same issue with externally compiled libs
(meaning lib projects are not part of the current solution). The
debugger won't go into the libs at all. The static libs are unmanaged C
++ compiled with clr support using the same vc8.0. Has anyone one
experienced anything like this? Could the default pdb file name
vc80.pdb for multiple projects cause any issue?

Thanks
zz

 

[Bruno van Dooren]

I have the same situation that I can't step into the unmanaged lib

code. The project debuger/mixed setting didn't have any effect on
this (I tried it instead of the default auto).
In my case I have 4 libs (unmanaged) compiled using a separate
solution and linked as static libs into the current solution (all
using vc++ 8 with clr support). Somehow I can only step into one of
the libs, but not the other three.

Try putting those projects in the same solution. That takes care of a lot of
problems usually.