I hate to say it, but it works for me...
Would you mind enabling the debugger's debug log and checking the debugger's output when the breakpoint is hit?
Maybe it has something to do with the path you have C::B in...
Yiannis.
ok, i've checked the debugger's debug log and found nothing out of the ordinary,
here's the log: (partly cleaned "..." from uninteresting stuff)
> directory D:/cpp/_PROJE~1/CODEBL~1/_HEAD/src/
> file devel/codeblocks.exe
> set args --debug-log --no-check-associations -ns
> cd devel
> delete
> tbreak app.cpp:181
> set confirm off
> set disassembly-flavor intel
> run
...
frame-begin 0 0x402565
frame-function-name
CodeBlocksApp::InitFrame
frame-args
arg-begin
arg-name-end
arg-value *
arg-end
frame-source-begin
frame-source-file
src/app.cpp
frame-source-file-end
frame-source-line
181
frame-source-end
source D:/cpp/_PROJE~1/CODEBL~1/_HEAD/src/src/app.cpp:181:6659:beg:0x402565
frame-end
stopped
...
> info args
Current language: auto; currently c++
...
this = (CodeBlocksApp * const) 0x103e370
...
> info locals
frame = (class MainFrame *) 0x106de48
...
debugging was working well, breakpoints reached and single-stepping was working properly,
also watch-variables were displayed properly, but the actual line in the editor window was not
highlighted as i described earlier.
i tried several possible things but without success.
as a last resort i cleaned the whole project and rebuilt everything - now it works again !
an imaginable theory could be:
i updated last week the gcc compiler from 3.4.2 to 3.4.4 and i'm sure that i rebuilt
codeblocks completely after upgrading the compiler, but then i didn't delete all object files
explicitly but i did a "Project rebuild".
today i deleted all former compilation products by hand and started the "Project rebuild" afterwards.
Thank God!
Now it works again properly !and ... sorry for the false alarm !