Setting breakpoints in a mixed mode file?

[PeteOlcott]

When I set a break point in a file that has both managed C++ and
unmanaged C++ the debugger never sees the breakpoints in the managed
code. What can be done to get the debugger to "see" the breakpoints in
the managed code?

 

[David Lowndes]

When I set a break point in a file that has both managed C++ and

unmanaged C++ the debugger never sees the breakpoints in the managed
code. What can be done to get the debugger to "see" the breakpoints in
the managed code?

Have you enabled the mixed mode debugging option?

Dave

 

[PeteOlcott]

Have you enabled the mixed mode debugging option?

Dave

I just tried that on the project (of hundreds of projects in a single
solution) that has the managed C++ code, and I got the hollow red dot,
indicating that the breakpoint will not be reached. I do know that the
line of code that the breakpoint is on, was reached because it prints
its output to a file. However the breakpoint itself is never tiggered.

 

[PeteOlcott]

Have you enabled the mixed mode debugging option?

Dave

(This may be a duplicate message, Google Groups was having problems).
I tried this and the red dot indicating the breakpoint was hollow,
(meanig that it will not be triggered) even though I know that the
line of code was reached because it printed its output line to the
output file.

 

[David Lowndes]

Have you enabled the mixed mode debugging option?

I just tried that on the project (of hundreds of projects in a single
solution) that has the managed C++ code, and I got the hollow red dot,
indicating that the breakpoint will not be reached.

Peter,

I think you have to set it on the project that you're debugging, so if
they're not the same, that may be the issue.

To check if that is the issue, if you start the program outside the
debugger and then attach to that process, the attach process dialog
allows you to select what type of debugging you want to do.

Dave

 

[PeteOlcott]

Peter,

I think you have to set it on the project that you're debugging, so if
they're not the same, that may be the issue.

To check if that is the issue, if you start the program outside the
debugger and then attach to that process, the attach process dialog
allows you to select what type of debugging you want to do.

Dave

I don't know how to attach to a process. As it is the system is
already comprised of very many processess.

 

[David Lowndes]

I don't know how to attach to a process.

In visual studio, use the Tools, Attach to Process menu item.
In the Attach to Process dialog box, look at the "Attach To" controls
- they allow you to select the type of code (native, managed, script).

As it is the system is already comprised of very many processess.

Select the process that is the one you want to debug. It's your
system!

Dave