Board index » cppbuilder » Debug tracing off

Debug tracing off


2006-10-21 03:45:37 AM
cppbuilder77
I am using BCB 6 (personal edition) and have an annoying problem when using
the IDE de{*word*81}.
Many times if I just MAKE the program the tracing function loses track of
the correct line. The highlighted line is not the next line that executes.
In many instances this is not obviously apparent and I search for code
errors in vain. Rebuilding the project fixes the problem but obviously would
not want to rebuild everytime.
I just have the debug button checked in the compiler options and cannot see
any obvious switch that might affect this other than Optimization which is
NONE by default of the debug mode.
I have seen this problem in all IDE's I have ever worked with (not that
many). In one I finally traced it down to the way the newline character was
handled in the editor.
Let me know if I am doing something stupid, wrong or if there are any tricks
to minimizing the problem.
Thanks in advance for any help.
Bill Riley
XXXX@XXXXX.COM
 
 

Re:Debug tracing off

Hi Bill,
In a word, no you are not doing anything stupid.
(Or even wrong...)
I think your observation about the ubiquitousness
of this is accurate as well.
I was not aware of the newline handling aspect but
it sounds logical as well.
As I think you may have guessed the failure of the
code displayed to synchronize with the recompiled code
when not doing a complete (re)Build is very common.
I have also seen this when the compiler 'optimizes'
code. This occurs in some form whether 'Optimizations'
are turned on or not.
For example where you have code that processes data that
is never accessed (if you have not written that section
yet for example). Sometimes the de{*word*81} gets out of sync.
Being as there is no underlying assembly code to sync too.
HTH,
Bruce
 

Re:Debug tracing off

Bruce,
Thanks for the comments. I had forgotten that most compilers now still will
do some simple optimizations even with optimization turned off.
Did not think about unaccessible code, will look for that next time.
Bill
"Bruce Larrabee" < XXXX@XXXXX.COM >wrote in message
Quote

Hi Bill,

In a word, no you are not doing anything stupid.
(Or even wrong...)

I think your observation about the ubiquitousness
of this is accurate as well.

I was not aware of the newline handling aspect but
it sounds logical as well.

As I think you may have guessed the failure of the
code displayed to synchronize with the recompiled code
when not doing a complete (re)Build is very common.

I have also seen this when the compiler 'optimizes'
code. This occurs in some form whether 'Optimizations'
are turned on or not.

For example where you have code that processes data that
is never accessed (if you have not written that section
yet for example). Sometimes the de{*word*81} gets out of sync.
Being as there is no underlying assembly code to sync too.

HTH,

Bruce
 

{smallsort}