User forums > Help

Code::Blocks hangs while debugging

<< < (5/5)

Pecan:

--- Quote from: TF on May 01, 2006, 01:23:36 am ---
--- Quote from: Pecan on May 01, 2006, 12:25:15 am ---The input would be at the same location to which the output went.
It's up to the program or the programmer to start the shell, not CB's
Currently, both are in std::I/O limbo...

I believe this is a programmer err, a logic err, an oversight....
Poor CB is the object of an injust accusation. :)

--- End quote ---

As I run the program with gdb, all messages appears like in C::B's debugger(debug) task but with gdb I can input a string ... Therefore I assume that C::B should anticipate the input in the debugger task, too ...

Did you ment in your post that this behaviour is caused by a C::B programmer err or a logic err in C::B ?  :? If so I should create a bug report ...

Best regards,

Thomas

--- End quote ---

I'm conficted as to wheither this is a bug or not. gdb is a shell task, so you, as a programmer, can expect to have access to std i/o.  But CB is a graphics task without shell access. So I, as a programmer, would not expect to have std I/O access unless I provided the means to access it.

I'd submit this as a bug anyway, and see how the core devs react. Don't get upset if they yell at ya though. This might be cause for yelling.... :x

TF:
Hi Pecan,

thanks for information 8)

I've submitted this problem and hope the developer can fix it and won't yell too loud against me ;)

Best regards,

Thomas

Navigation

[0] Message Index

[*] Previous page