News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

C::B doesn't stop at breakpoints

Started by ninio_arg, January 04, 2014, 09:03:09 AM

Previous topic - Next topic

ninio_arg

I know, I know. This is not a news. I've read the posts about this issue on this forum, but I couldn't fix it.

I'm on Slackware 14.1 and I've compiled CB 12.11 from the sources. I'm trying a simple C++ Hello Wold-like program just to check this problem.
I read this http://wiki.codeblocks.org/index.php?title=Debugging_with_Code::Blocks and everything is fine (-g option, etc).
I don't have any space at the project path or at the C::B path.
When I run gdb executable from a terminal, it says that symbols were loaded. So, -g is working.

I don't know what to do :S

oBFusCATed

Enable and post the full log from the debugger.
Does in terminal gdb stop at breakpoints?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ninio_arg

Quote from: oBFusCATed on January 04, 2014, 11:29:13 AM
Does in terminal gdb stop at breakpoints?
Yes, it does.

Quote from: oBFusCATed on January 04, 2014, 11:29:13 AM
Enable and post the full log from the debugger.
How can I do it?.

oBFusCATed

Settings -> Debugger -> Common -> Full log...

Then right click -> copy to clipboard
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ninio_arg

Sorry, but I don't know what or where is the output. The "Debugger" tab in "Log & others" is empty. :S

ollydbg

Quote from: ninio_arg on January 05, 2014, 01:09:41 AM
The "Debugger" tab in "Log & others" is empty. :S
It will have texts when your start the debugging.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

ninio_arg

Quote from: ollydbg on January 05, 2014, 03:02:20 AM
Quote from: ninio_arg on January 05, 2014, 01:09:41 AM
The "Debugger" tab in "Log & others" is empty. :S
It will have texts when your start the debugging.
That's the problem. It hasn't. Even when the program stops waiting for an input.

ollydbg

Quote from: ninio_arg on January 05, 2014, 03:10:40 AM
Quote from: ollydbg on January 05, 2014, 03:02:20 AM
It will have texts when your start the debugging.
That's the problem. It hasn't. Even when the program stops waiting for an input.
Strange, please tell us the exact steps you did. Thanks.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

ninio_arg

I open my project (.cbp). The build target is "Debug". I click on Build (or Rebuild). After checking the tab "Build messages" and see everything is fine, I put my breakpoints and I click on "Run".
Breakpoints aren't read, and if the program stops at some user input, the "Debugger" tab is empty. Indeed, it's empty all the time.

ollydbg

Quote from: ninio_arg on January 05, 2014, 07:45:40 AM
I open my project (.cbp). The build target is "Debug". I click on Build (or Rebuild). After checking the tab "Build messages" and see everything is fine, I put my breakpoints and I click on "Run".
Breakpoints aren't read, and if the program stops at some user input, the "Debugger" tab is empty. Indeed, it's empty all the time.
Note, you should click the "Debug/Continue" button, not "Run" button to start debugging.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

ninio_arg

#10
Quote from: ollydbg on January 05, 2014, 07:59:25 AM
Quote from: ninio_arg on January 05, 2014, 07:45:40 AM
I open my project (.cbp). The build target is "Debug". I click on Build (or Rebuild). After checking the tab "Build messages" and see everything is fine, I put my breakpoints and I click on "Run".
Breakpoints aren't read, and if the program stops at some user input, the "Debugger" tab is empty. Indeed, it's empty all the time.
Note, you should click the "Debug/Continue" button, not "Run" button to start debugging.
OMG!!. What a shame!!. Yes sir, that's all!. Just use Start / Continue (F8), and not Run (F9).

Thank you so much!.

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]