Code::Blocks Forums
User forums => Help => Topic started by: m.29 on May 09, 2011, 11:27:23 pm
-
Hi, I have some problem with executing Code::Blocks after updating on Ubuntu 11.04.
I downloaded debugger_branch sources from SVN and tried to compile them. Compilation is OK so I executed ./update script like before (on previous version of Ubuntu). Then I tried to start C::B but GUI is broken (http://dl.dropbox.com/u/22120595/ubuntu-bad-cb.png) and no plugin is loaded. After opening any project I get "Deactivating the compiler plugin is most unwise." message. In Plugin manager there are no plugins visible.
I tried some advises that I found on this forum but nothing fixed it. Has anyone an idea what am I doing wrong?
-
You can try to do a clean checkout or at least remove the debug and the output folders manually and delete include/*.gch .
To get a more meaningful otput you can change wxLog::EnableLogging(false); at the beginning of OnInit() in app.cpp to wxLog::EnableLogging(true);
-
To get a more meaningful otput you can change wxLog::EnableLogging(false); at the beginning of OnInit() in app.cpp to wxLog::EnableLogging(true);
Reminds me: I wanted to make this an option via the command line or enabling it by default if you aklso enable the debug log.Would that be a good thing to do, probably?!
-
I had a patch for this here, but it got lost somewhere.
I enabled it by default and only disabled it, if the appropriate parameter was not set, so we get all messages from the start.
We have to fix the version-numbers of some xrc-files if I remember correctly, otherwise we would get some errors on startup.
-
Thanks, I noticed that I had some old test plugins in directory ~/.codeblocks/share/codeblocks/plugins. After I deleted the directory ~/.codeblocks/share/ plugins are loaded and GUI is OK :-)
But during closing of C::B there are some SIGSEGVs related to malloc (http://dl.dropbox.com/u/22120595/1st-sigsegv.png) and raise function (http://dl.dropbox.com/u/22120595/2nd-sigsegv.png)?
I tried all of this on clean SVN revision. But in the newest r7140 there were some radical changes so I tried it also on clean r7139 and SIGSEGVs are there, too.
-
I've seen this, too, it is on the block allocator. I don't know what is causing it.