Did you disable them and tried again? ...that's what i want to try , but no go until all plugins are present, because C::B invokes by default all of them if detected,
Are you using the very latest builds? A crash-on-close bug in EditorManager was fixed only 2 days ago.svn 1701 - its VERY recent :D
Did you try removing the respective shared libs from the plugins folder? They may not be rebuilt, just be left over from before.i first tried with
make clean should also have worked (but probably not after a ./configure without --enable-contrib parameter)
I can confirm that, I have these crashes, too.Are you using the very latest builds? A crash-on-close bug in EditorManager was fixed only 2 days ago.svn 1701 - its VERY recent :D
i have these ominous chrashes since the introduction of wxaui
1.) just run CodeBlocks and exit by File->QuitThe backtrace for the first test is exactly what I get. I didn't test the second one, but I would guess its the same result as you got.
2.) run C::B, open a project and say File->Close Project
Could you update to 1702 and try again? I must have fixed it now.test it soon - i'll report in approx. one hour ...
It is just an assumption but to me it looks as if during the normal deconstruction of all objects/plugins/etc. the codecompletion parser calls wxSafeYield and this functions then starts (through some other calls) a new message loop that has obviously nothing to do. Thus it waits for events that will never occour because everything is already disabled.That's why I asked if you had tried disabling the code completion plugin. This is exactly what I suspected, too. And worse, in its log function, the code completion plugin uses a plain normal wxYield.
...
Revision 1707 compiles fine again :)
So... let's see if the bug has silently gone away... :)
configmanager.cpp:226: error: no 'ConfigManager* CfgMgrBldr::GetConfigManager(const wxString&)' member function declared in class 'CfgMgrBldr'
configmanager.cpp: In member function 'ConfigManager* CfgMgrBldr::GetConfigManager(const wxString&)':
configmanager.cpp:228: error: no matching function for call to 'CfgMgrBldr::Get()'
./configmanager.h:254: note: candidates are: static ConfigManager* CfgMgrBldr::Get(const wxString&)
configmanager.cpp: At global scope:
configmanager.cpp:232: error: no 'ConfigManager* CfgMgrBldr::Build(const wxString&)' member function declared in class 'CfgMgrBldr'
configmanager.cpp: In member function 'void ConfigManager::Delete()':
configmanager.cpp:593: error: no matching function for call to 'CfgMgrBldr::Get()'
./configmanager.h:254: note: candidates are: static ConfigManager* CfgMgrBldr::Get(const wxString&)
configmanager.cpp: In member function 'void ConfigManager::DeleteAll()':
configmanager.cpp:609: error: no matching function for call to 'CfgMgrBldr::Get()'
./configmanager.h:254: note: candidates are: static ConfigManager* CfgMgrBldr::Get(const wxString&)
make[4]: *** [configmanager.lo] Error 1Finally fixed the hang in 1709 :)
Has Code::Blocks officially frozen its features set in an effort to squash all the finals bugs before the full 1.0 release?
I was just wondering why Code::Blocks is going through all these changes after 2 release candidates.I once had the same question (see http://forums.codeblocks.org/index.php?topic=1406.0 (http://forums.codeblocks.org/index.php?topic=1406.0)). Meanwhile I think the changes are definitely worth it. There are drastic changes but even I am using a new build from time to time it just get's better. And that's what should be. So my worries are gone... but that's just me.