User forums > Using Code::Blocks

Debugging on the Fedora Core 6 Nov 11 version

<< < (2/3) > >>

Tornado:
I have the exact same problem, debugger flags are set. I am not sure that this is even supported at this time, looking at the bug tracker. Really nice IDE, please make this option a priority.

Great work

MortenMacFly:

--- Quote from: goetz on November 16, 2006, 12:01:39 am ---when I go to the next line, no output window opens.

--- End quote ---

--- Quote from: Tornado on November 16, 2006, 08:58:43 am ---I am not sure that this is even supported at this time, looking at the bug tracker.

--- End quote ---
What do you mean??? What window shall open? C::B informs about debugging events in the debug log. I have no experiences with debugger versions above 6.3.x but this maybe a feature I don't know.
Please (if possible) create a very simple demo project and post it (zipped) into this thread including a step-by-step instruction what you do and what you expect to happen. I guess I simply don't understand.

Another option: Do you try to debug into a constructor? This is *not* supported natively by gdb but there is a work-around for this... Again: A demo project would be of much help.

With regards, Morten.

thomas:
I think he expects a console window that shows the text which he is pushing to cout.

@goetz:
After you made sure that you enabled debugging symbols, did you also make sure you disabled stripping?
This may sound like a stupid thing, but it actually happens that you forget to turn off stripping, and then you try and try, and it just won't work... I've had it happen many times.

Tornado:
Maybe I was not clear enough, what I'm talking about is on FC6 C::B does not have a console to take input for the debugger.  debugging works for the most part, with that exception...it shows the symbols, etc.

Game_Ender:
Well CB does not show a console window on linux.  You are just going to have live with it or (like Xcode) create a debugger terminal which lets you interact with GDB from the command line (way better than the "send command" message box), as well as handle stdin/stdout.

Navigation

[0] Message Index

[#] Next page

[*] Previous page