Author Topic: can't compile with [-g] correctly  (Read 5806 times)

Offline polisbul

  • Multiple posting newcomer
  • *
  • Posts: 17
can't compile with [-g] correctly
« on: January 03, 2013, 10:41:54 am »
I'm using ubuntu 10.04 and codeblocks 10.05, and can't compile correctly with [-g] option for debugging. debug mode seems not to work (debugger shows me only symbols and codes, not code lines). [-g] is the only option enabled. outside codeblocks ddd works fine, so i suppose it's a compiling error.
any hint?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
(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 polisbul

  • Multiple posting newcomer
  • *
  • Posts: 17
Re: can't compile with [-g] correctly
« Reply #2 on: January 03, 2013, 12:37:29 pm »
checked all those pages, but nothing changes...
I still get this message:

warning: GDB: Failed to set controlling terminal: Operation not permitted
« Last Edit: January 03, 2013, 12:41:39 pm by polisbul »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: can't compile with [-g] correctly
« Reply #3 on: January 03, 2013, 12:59:38 pm »
Have you tried to search about this warning?
(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 Jenna

  • Administrator
  • Lives here!
  • *****
  • Posts: 7252
Re: can't compile with [-g] correctly
« Reply #4 on: January 03, 2013, 01:00:01 pm »
checked all those pages, but nothing changes...
I still get this message:

warning: GDB: Failed to set controlling terminal: Operation not permitted

It's the first time you post about this message.
So it looks like you are not able or willing to give the needed information to evn try to help you.

And as you can see it's a warning message, not an error.
Search the web for it and youz will see it's a gdb, not a C::B issue, but it does not harm in any way.
Debugging usually works fine with C::B.