By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,088 Members | 1,326 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,088 IT Pros & Developers. It's quick & easy.

Breakpoints and Visual Studio 2005

P: n/a
One Visual Studio 2005 solution contains a C# project and C++ ATL DLL
project. The DLL compiles fine, gets registered automatically, gets
referenced correctly when the C# program compiles, and gets called correctly
during execution. So far, so good.

During execution of the DLL, a call to the ATL/MFC shared library method
CImage::Create returns FALSE.[*] So I tried to set a breakpoint before the
call.

When not executing, Visual Studio displays a brown dot saying that the
breakpoint is valid. When executing, Visual Studio displays a mostly
transparent dot with an exclamation mark saying that the breakpoint is not
valid. I can right-click the dot and set an option for the "place" of the
breakpoint, but it doesn't matter. The breakpoint never gets hit.

When I add and remove calls to the Win32 API MessageBox, they get executed
correctly. So the DLL is getting recompiled properly and executed properly,
only the breaker is broken.

Does anyone know how to get breakpoints working?

[* I don't need help with this failure at this moment. I only need help
with getting breakpoints working.]

Sep 19 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Norman,
One Visual Studio 2005 solution contains a C# project and C++ ATL DLL
project. The DLL compiles fine, gets registered automatically, gets
referenced correctly when the C# program compiles, and gets called
correctly during execution. So far, so good.
...
When not executing, Visual Studio displays a brown dot saying that the
breakpoint is valid. When executing, Visual Studio displays a mostly
transparent dot with an exclamation mark saying that the breakpoint is not
valid. I can right-click the dot and set an option for the "place" of the
breakpoint, but it doesn't matter. The breakpoint never gets hit.
Two things:
1) are you using debug builds?
2) did you enable mixed debugging for managed und unmanaged code?
Project->Properties->Debug "Enable unmanaged code debugging"

--
SvenC

Sep 19 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.