Re: Strange Debugger Problems
- From: "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
- Date: Fri, 1 Jul 2005 14:31:18 +0300
> What gives? Why can I hit f5 to and debug with no problem when I pretend my
> non-managed project is a managed project by using the "/clr" option? Is there
> a difference between the debuggers that managed c++ and non-managed c++ use?
> If so this may lead me to finally figure out how to fix my problem.
>
Yes, there are different debug engines used by VS.NET when debugging managed
and unmanaged applications (called Native and CLR, respectively). They can be used
separately, or they can be used together (mixed mode, or interop).
There are two ways to specify the engine:
1) Using project settings
Project properties | Configuration Properties | Debugging | Debugger Type
(though I remember that in a previous message you said that it's "Auto", which
is usually good enough - anyway, what setting is there now? What happens
if you try other settings?)
2) When attaching to the running application
(in Attach to Process dialog, you can select "Common Language Runtime" or "Native"
engine, or both - which do you use?)
>From your description it looks like the debugger has a problem choosing the correct
debug engine for the application when it is starting under debugger, though does not
have this problem when attaching to it (if you choose "Native" in Attach to Process
dialog, of course). Take a look at the information here, may be there is something
that can help:
http://blogs.msdn.com/greggm/archive/2004/07/08/177774.aspx
Oleg
.
- Follow-Ups:
- Re: Strange Debugger Problems
- From: jbacigal
- Re: Strange Debugger Problems
- Next by Date: Reconnect to MSVCMON after network failue?
- Next by thread: Re: Strange Debugger Problems
- Index(es):
Relevant Pages
|
Loading