User forums > Using Code::Blocks
"Break Debugger" button has never worked.
Alpha:
--- Quote from: zeroth on December 12, 2013, 02:01:24 am ---Well, I can't create a new project because.. uh, well... that's another problem - I can't make a new project: http://img689.imageshack.us/img689/8692/j72h.png
--- End quote ---
Do you have the Scripted Wizard plugin installed?
zeroth:
--- Quote from: Alpha on December 12, 2013, 07:28:47 pm ---
--- Quote from: zeroth on December 12, 2013, 02:01:24 am ---Well, I can't create a new project because.. uh, well... that's another problem - I can't make a new project: http://img689.imageshack.us/img689/8692/j72h.png
--- End quote ---
Do you have the Scripted Wizard plugin installed?
--- End quote ---
Looks like it wasn't enabled, I can now create new projects.
--- Quote from: oBFusCATed on December 12, 2013, 02:08:17 am ---
--- Quote from: ollydbg on December 10, 2013, 07:06:34 am ---I guess the log messages from your app have affect on the C::B debugger parser.
--- End quote ---
I don't see the pid in the log, sometimes this happen, because no thread is started and gdb fails to print the pid.
I have to do something about this, but I'll see I find some time.
--- End quote ---
If it helps your investigation, it may also be along the same lines as another problem I'm having: if I set or remove breakpoints during program execution (when the debuggee is not stopped at a breakpoint), codeblocks will usually freak out and not allow me to stop the debugger once I exit the debugee, even if the process no longer exists. I will provide a debugger log if you would like.
--- Quote from: ollydbg on December 10, 2013, 07:06:34 am ---
--- Quote from: zeroth on December 12, 2013, 02:01:24 am ---I can't imagine the CB team would code the interactions between CB and GDB in such a rinky-dink manner as to just interpret GDB screen output, so it seems they didn't anyway.
--- End quote ---
Unfortunately this is how it works...
--- End quote ---
Well I don't know anything about how GDB communicates with frontends, so if that's how it's gotta be done, then that's how it's gotta be done. It doesn't seem to be my problem here anyhow since I've already disabled all of my stdout/err output.
oBFusCATed:
It is not the correct way. Hopefully in the future we'll use the more robust GDB/mi protocol, but for now this is how it works.
Removing all your stdout code won't help.
zeroth:
Aye. That's one of the features I like about CodeLite, it seemed to have better debugger integration. But don't worry, I still prefer CodeBlocks ;)
PS, I updated my previous reply.
liss719:
I have the same thing. I use CB to develope the arm system. When debug use gnu arm gdb debugger to debug my code, if I don't set any breakpoint, I will can't break or stop the debugger, even the "Break Debugger" or "Stop Debugger" button.
I use the CB 13.12 RC2 now, I can't create ARM project use the wizard. Do you have the same thing?.....
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version