Debugging rows doesn't match

[Ol eg Da nu]

Hi C++-ers,

I have this strange problem debugging a project. I have a cpp which
creates me problems debugging, I mean when I get to the brakepoint and
trying to step over, it seems like to me that the debugging area is
not the same what I see. I f you understand me correctly... debugging
cursor does not pass over empty rows of the code, and vice-versa in
some cases it overpasses coded rows. I made a test... I was stepping
in from a point and when I step in a simple row, it steps in a
function that is 3 rows bellow. So debugging info doesn't match what I
see. What can I do to repair it, I tried to rebuild the project and
nothing helped??

[David Lowndes]

Post by Ol eg Da nu
I have this strange problem debugging a project. I have a cpp which
creates me problems debugging, I mean when I get to the brakepoint and
trying to step over, it seems like to me that the debugging area is
not the same what I see. I f you understand me correctly... debugging
cursor does not pass over empty rows of the code, and vice-versa in
some cases it overpasses coded rows. I made a test... I was stepping
in from a point and when I step in a simple row, it steps in a
function that is 3 rows bellow. So debugging info doesn't match what I
see. What can I do to repair it, I tried to rebuild the project and
nothing helped??

What you describes sounds like what happen if you debug a release
(optimised) version.

heck that you're building and running the debug configuration, and
that the options for the compiler for the debug configuration have
optimizations disabled.

Dave

[Scot T Brennecke]

Or, an alternative to what David suggested, it sounds like your symbol file is out of sync from your sources. Perhaps you did not
do your most recent build with the /Zi for compile and /DEBUG for link?

Post by Ol eg Da nu
Hi C++-ers,
I have this strange problem debugging a project. I have a cpp which
creates me problems debugging, I mean when I get to the brakepoint and
trying to step over, it seems like to me that the debugging area is
not the same what I see. I f you understand me correctly... debugging
cursor does not pass over empty rows of the code, and vice-versa in
some cases it overpasses coded rows. I made a test... I was stepping
in from a point and when I step in a simple row, it steps in a
function that is 3 rows bellow. So debugging info doesn't match what I
see. What can I do to repair it, I tried to rebuild the project and
nothing helped??

[debugeasy]

Post by Ol eg Da nu
Hi C++-ers,
I have this strange problem debugging a project. I have a cpp which
creates me problems debugging, I mean when I get to the brakepoint and
trying to step over, it seems like to me that the debugging area is
not the same what I see. I f you understand me correctly... debugging
cursor does not pass over empty rows of the code, and vice-versa in
some cases it overpasses coded rows. I made a test... I was stepping
in from a point and when I step in a simple row, it steps in a
function that is 3 rows bellow. So debugging info doesn't match what I
see. What can I do to repair it, I tried to rebuild the project and
nothing helped??

Two possible:
1. You were debugging program with a optimized release version.
2. The symbols included in the exe don't match the code.

for the first possible, like David Lowndes said, configure your
compile and link option.

for the other, rebuild all your code to make the exe containing the
exact symbols.

hope you can know my meaning.