Author Topic: Compiler is not working / not stopping at breakpoints  (Read 3778 times)

Offline Louis-Philippe

  • Single posting newcomer
  • *
  • Posts: 4
Compiler is not working / not stopping at breakpoints
« on: April 30, 2012, 03:13:36 pm »
Hi everyone,

I am using ubuntu 11.10 (and GNU GCC compiler) and I am having trouble getting the debugger to work, I try to set breakpoints but the compiler just does not pause when passing them. (Even when I create a new "hello world" project.)

I have already looked around for a solution on this forum and elsewhere, but I have not found the problem yet.

My directories only include normal and capital letters, so there should be no issue with incorrect file paths with strange symbols causing problems.
I have also checked the debugger settings and have set these in the same way as illustrated in the wiki here: http://wiki.codeblocks.org/index.php?title=Debugging_with_Code::Blocks

I have also re-installed and rebooted, and I have tried resetting the compiler settings to default.

Help would be greatly appreciated!

Regards

LP


« Last Edit: April 30, 2012, 03:16:55 pm by Louis-Philippe »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: Compiler is not working / not stopping at breakpoints
« Reply #1 on: April 30, 2012, 03:39:18 pm »
I try to set breakpoints but the compiler just does not pause when passing them.
What does this mean? Compiler or debugger? Pause or stop?

Do you have the -g option enabled and -s option and optimization options disabled?
Have you looked at the full log of the debugger?
Any errors in it?

What is your version of C::B?
(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!]

Offline Louis-Philippe

  • Single posting newcomer
  • *
  • Posts: 4
Re: Compiler is not working / not stopping at breakpoints
« Reply #2 on: May 02, 2012, 02:59:34 pm »
I meant that the debugger was not pausing when executing the program.

Whatever the problem was it seems to have resolved itself since I booted my machine this morning.

Nevertheless thank you for your response to my question!

Regards,

LP