User forums > Help

Breakpoint Being Ignored <with full debugger log>

<< < (2/7) > >>

dcbdbis:
I have a fix, but no reason why......

I know I got a little draconian.....but I went into my home dir and nuked ".codeblocks".

I know I lost all my fonts and colors, but something had to be wrong on my end, or the forums would be full of similar issues, and they are not.

Fired up C::B.......And my breakpoints work perfectly!

I have no idea why...


But I do appreciate your help!


Sincerely,


Dave

dcbdbis:
Well,

I marked this solved too soon. The debugger works about 15% of the time. The other times, it ignores the breakpoints still

Sincerely,


Dave

oBFusCATed:

--- Quote from: dcbdbis on December 13, 2013, 05:01:32 am ---I can manually debug the program and it breaks properly when I open a terminal, and run gdb from the CLI. Then I specify "gdb sourcefilename:linenum". It works peechee, so my system's setup appears to be OK.

--- End quote ---
If you re-read the steps I've depicted you'll see that I'm asking you to test if debugging works from a terminal started by Code::Blocks.
I have the same problem and I'm trying to find why it happens. It is very strange problem, because gdb works fine from a normal terminal 100% of the time,
but started from C::B it fails and the failures are pretty strange. If it works once it will always work in this instance of C::B, but if it fails it will always fail until a restart of C::B.
Also it fails when started from a terminal started by broken instance of C::B. :'(

The current workaround is to restart C::B until it works and then use it without restarting it.
Can you confirm that this workaround works for you, too?

dcbdbis:
Here is a screen cap of the C::B CLI.

It ignored the breakpoint.

Thanks again for your help.

Sincerely,

Dave

oBFusCATed:
Grrrrhhhhhh....

Jens: Have you tried to debug something on a recent Fedora? Does it work there?

Navigation

[0] Message Index

[#] Next page

[*] Previous page