User forums > Help

Issues with GDB and C::B

(1/2) > >>

nore:
Hello all,

I seem to be having trouble with Code::Blocks tonight after working to implement text-field highlighting in an OpenGL-based system. It seems that my debugger will only recognize breakpoints that are placed *before* starting the program--it will not recognize breakpoints placed during runtime as it usually does. I also noticed that the red 'x' icon used normally to stop the debugger and program execution does not work as usual. I only recall this happening once before. Does anyone have any suggestions as to what might be the cause of this strange error?

-nore

Pecan:

--- Quote from: nore on February 02, 2025, 05:27:34 am ---Hello all,

I seem to be having trouble with Code::Blocks tonight after working to implement text-field highlighting in an OpenGL-based system. It seems that my debugger will only recognize breakpoints that are placed *before* starting the program--it will not recognize breakpoints placed during runtime as it usually does. I also noticed that the red 'x' icon used normally to stop the debugger and program execution does not work as usual. I only recall this happening once before. Does anyone have any suggestions as to what might be the cause of this strange error?

-nore

--- End quote ---

This usually happens to me when I've set the default debugger to the wrong debugger config.

Check that the MainMenu>Debug>Active debugger is set as you expect.
Check that MainMenu>Settings>Debugger of the Active debugger (above) is as you expect.

nore:
I've got my settings configured as usual. I will try setting up another project to see if that fixes the issue.

nore:
Even rebuilding the project and configuring the compiler, linker, and debug settings as project settings rather than global settings seems to result in the same issue. I remember this error occurring maybe six weeks ago and it was solved by building the project using global compiler settings rather than project-local compiler settings. Run-time breakpoints are still ignored as if the debugger is not running.

nore:
Looking at the Debugger Log in Code::Blocks I see that the executable attempts to interrupt the process as usual--nothing "funny" shows up in the log; and placing a breakpoint before launching, then removing the breakpoint in real-time seems to stop the Debugger from crashing in with its useful tools at function call--but trying to *place* a breakpoint during real-time/run-time does not seem to catch the Debugger's attention, as is evident in this screenshot where I try to evoke the debugger using a breakpoint on the frequently-called "draw()" function in my program.

Navigation

[0] Message Index

[#] Next page