Bizarre behaviour in VS2005 when debugging

[pinkmonkey4ever]

I have a VC6 ANSI C (console) project that I have recompiled sucessfully
under VS2005.

However, when I attempt to debug the code (step through) - my
breakpoints are disabled (msg : "beakpoints will not be hit"), and worse
still - I find that instead of steopping through my code, I am stepping
through a file named crt.exe - which guessing from the function names in
the file (as well as the file name itself) - is something to do with the
CLR (i.e. .Net stuff).

I can't understand how this can be. This is a simple ANSI C console
project that makes ABSOLUTELY NO use of the CLR. I've checked and
re-checked my project settings and AFAICT, everything looks ok - also, I
am at my wits end. Does anyone have an idea as to what may be causing
this bizzare behaviour?

 

[pinkmonkey4ever]

I have a VC6 ANSI C (console) project that I have recompiled sucessfully
under VS2005.

However, when I attempt to debug the code (step through) - my
breakpoints are disabled (msg : "beakpoints will not be hit"), and worse
still - I find that instead of steopping through my code, I am stepping
through a file named crt.exe - which guessing from the function names in
the file (as well as the file name itself) - is something to do with the
CLR (i.e. .Net stuff).

I can't understand how this can be. This is a simple ANSI C console
project that makes ABSOLUTELY NO use of the CLR. I've checked and
re-checked my project settings and AFAICT, everything looks ok - also, I
am at my wits end. Does anyone have an idea as to what may be causing
this bizzare behaviour?

Before someone suggests this (regarding the disabled breakpoints).
Although I am using a Dll (i.e. importing a .lib file), I have
recompiled the library and DOUBLE-Checked to make sure that I am linking
to the latest build of the library - as this was the first thing that
occured to me to check, when I wasn't able to set breakpoints..

 

[SvenC]

Hi,

I have a VC6 ANSI C (console) project that I have recompiled sucessfully
under VS2005.

However, when I attempt to debug the code (step through) - my breakpoints
are disabled (msg : "beakpoints will not be hit"), and worse still - I
find that instead of steopping through my code, I am stepping through a
file named crt.exe - which guessing from the function names in the file
(as well as the file name itself) - is something to do with the CLR (i.e.
.Net stuff).

I can't understand how this can be. This is a simple ANSI C console
project that makes ABSOLUTELY NO use of the CLR. I've checked and
re-checked my project settings and AFAICT, everything looks ok - also, I
am at my wits end. Does anyone have an idea as to what may be causing this
bizzare behaviour?

Did you build and run the debug version?

 

[pinkmonkey4ever]

Hi,




Did you build and run the debug version?

Erm ..., yes (I would have thought that was obvious from my post)

 

[Ben Voigt [C++ MVP]]

I have a VC6 ANSI C (console) project that I have recompiled sucessfully
under VS2005.

However, when I attempt to debug the code (step through) - my breakpoints
are disabled (msg : "beakpoints will not be hit"), and worse still - I
find that instead of steopping through my code, I am stepping through a
file named crt.exe - which guessing from the function names in the file
(as well as the file name itself) - is something to do with the CLR (i.e.
.Net stuff).

CRT simply means "C Runtime", and it is used by every C program regardless
of whether you also use the CLR. For example, printf is in the CRT library.

"crt.exe", on the other hand, sounds like a malware. The CRT is a lib or
dll, not an exe.