News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

The blind debugging: Run to cursor (no yellow bookmark): Watches window: blank

Started by AuSsIeStOnE, November 17, 2009, 11:28:39 AM

Previous topic - Next topic

AuSsIeStOnE

Hello,

I use Codeblocks v8.0.2 on Windows XP SP3 updated and installed on a virtual machine

Generally, when I use Run to cursor with next line and appears a yellow bookmark there, things works fine. The watches window show all variables in realtime mode (bugs can be easily discovered).

The blind debugging method: there are situations when I use Run to cursor (no yellow bookmark) and the next line button remains shadowed, the application run from start to end automatically and the Debugging Windows > Watches window: show nothing

Debugger name and version: GNU gdb 6.7.50.20071127
........................................
........................................
........................................
Program exited normally.
Debugger finished with status 0

Here are the Codeblocks settings:

Compiler and debugger settings: Global compiler settings: Produce debugging symbols: <checked>

Project: Build options...:
    - project name:
          - produce debugging symbols: <checked>
          - Enable all compiler warnings (overrides every other setting): <checked>
    - Debug:
          - Produce debugging symbols: <checked>
    - Release:
          - Strip all symbols from binary (minimizes size): <checked>
          - Optimize fully (for speed): <checked>
          - Optimize generated code (for size): <checked>

Anyone to know what's the problem and how to solve it ?!

Thanks

AuSsIeStOnE

Hello dudes,

I manually installed Code::Blocks SVN 5911 (Nights) with:
- wxmsw28u_gcc_cb.dll  (gcc 421)
- mingwm10.dll (wx 2810)



and the problem solved itself. Now I can debug applications with full options enabled (including the working Windows Watches)

NOTE:
MinGW with tdm-mingw-1.908.0-4.4.1-2.exe don't work (gdb-6.8 return errors ! it seems to be unstable)

Thanks anyway for your silent help ;-)