Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: artoj on January 13, 2006, 08:40:53 pm

Title: Display application's debug log broken
Post by: artoj on January 13, 2006, 08:40:53 pm
I guess we'll start talking about tooth fairies and unicorns in the nightly builds forums.

---

The display application's debug log seems to be broken. The setting does nothing.

Confirm or is this fixed in SVN (I'm using revision 1731) already?
Title: Re: Display application's debug log broken
Post by: killerbot on January 13, 2006, 08:51:55 pm
could well be, since yesterday I was not able to get anything out of it, had to fall back on message boxes ... ;-)
Title: Re: Display application's debug log broken
Post by: thomas on January 13, 2006, 08:56:28 pm
Just tried revision 1717 and revision 1750. Debug log works fine in both.
Title: Re: Display application's debug log broken
Post by: Michael on January 13, 2006, 08:57:36 pm
I do not know exactly what it should display, but when I select the option and re-started C::B, I would get Code::Blocks Debug. And it seems to work (I use rev1750):

Quote
Loading lexer_angelscript.xml
Loading lexer_cg.xml
Loading lexer_cpp.xml
Loading lexer_css.xml
Loading lexer_f77.xml
Loading lexer_glsl.xml
Loading lexer_gm.xml
Loading lexer_hitasm.xml
Loading lexer_lua.xml
Loading lexer_OgreMaterial.xml
Loading lexer_prg.xml
Loading lexer_rc.xml
Loading lexer_xml.xml
[20:53:29.781]: Loading toolbar...
[20:53:29.871]: AStylePlugin: loaded
[20:53:29.891]: ClassWizard: loaded
[20:53:29.922]: CodeCompletion: loaded
[20:53:29.962]: Added compiler "GNU GCC Compiler"
[20:53:29.962]: Added compiler "Microsoft Visual C++ Toolkit 2003"
[20:53:29.962]: Added compiler "Borland C++ Compiler 5.5"
[20:53:29.962]: Added compiler "Digital Mars Compiler"
[20:53:29.972]: Added compiler "OpenWatcom (W32) Compiler"
[20:53:29.972]: Added compiler "Intel C/C++ Compiler"
[20:53:29.972]: Added compiler "SDCC Compiler"
[20:53:29.972]: Compiler: loaded
[20:53:30.012]: Debugger: loaded
[20:53:30.052]: DefaultMimeHandler: loaded
[20:53:30.082]: PluginWizard: loaded
[20:53:30.112]: ToDoList: loaded
[20:53:30.112]: WindowsXPLookNFeel: loaded
[20:53:30.122]: Source code formatter (AStyle) plugin loaded
[20:53:30.122]: Class wizard plugin loaded
[20:53:30.132]: Code completion plugin loaded
[20:53:30.242]: Compiler plugin loaded
[20:53:30.392]: Debugger plugin loaded
[20:53:30.402]: Default MIME handler plugin loaded
[20:53:30.402]: Code::Blocks Plugin wizard plugin loaded
[20:53:30.422]: To-Do List plugin loaded
[20:53:30.422]: Windows XP Look'n'Feel plugin loaded
[20:53:30.542]: Running startup script

Michael
Title: Re: Display application's debug log broken
Post by: artoj on January 13, 2006, 09:01:59 pm
Just tried revision 1717 and revision 1750. Debug log works fine in both.

Yeah, it works here too, now. I didn't know you had to restart C::B. Maybe a message box stating that you need to restart that the changes take effect.

Requesting this thread to be closed.
Title: Re: Display application's debug log broken
Post by: Michael on January 13, 2006, 09:24:49 pm
Anyway, how to delete all or some text from Code::Blocks Debug. If I do e.g., a select all, then I can only perform a copy :?.

Michael

PS.: C::B rev1570.
Title: Re: Display application's debug log broken
Post by: killerbot on January 13, 2006, 09:27:05 pm
I am on your side Michael for that one, had a discussion about that with the devs 2 months ago ;-)
Title: Re: Display application's debug log broken
Post by: thomas on January 13, 2006, 09:27:17 pm
You cannot. That's not a feature :)
Title: Re: Display application's debug log broken
Post by: Michael on January 13, 2006, 09:32:07 pm
You cannot. That's not a feature :)

Ok, I understand. You can just copy (which is already useful :)). Thank you.

Michael