News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Getting stderr output in the debug window.

Started by immortalsoFar, December 04, 2016, 08:43:20 AM

Previous topic - Next topic

immortalsoFar

I'm pretty certain we used to be able to printf/sprintf to stderr and the output be shown somewhere but now that's no longer the case.

Running Codeblocks from a console doesn't do the trick.

I can redirect stderr with freopen but seeing the errors (eg GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed) as they happen is somewhat important. Setting Settings/Debugger/Full (debug) log does show the stderr output in the debug window but it also shows every damned watched variable, stack frame etc as well every single time a breakpoint is hit which makes it, to all intents and purposes, useless.

How can I get the stderr output without the corresponding junk in the debugging window?

Thanks.

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!]