User forums > Using Code::Blocks

how to get rid of contribs enabled ???

<< < (4/6) > >>

tiwag:
ok - here it is   8)

what i did : a fresh install of C::B without contrib plugins
by using the following commands

make clean
make clean-zipfiles
sudo make uninstall
svn update  ->(to SVN rev 1702)
./configure
make
sudo make install


1.) then i ran C::B and got NO CRASHES by simply running and closing C::B  :)

2.) the next time i ran C::B and changed the toolbar positions and some other layout-changes,
closed C::B, saved the changed layout, and got NO CRASH :)

3.) the next time i ran C::B and opened a project, edited something, saved the files and the project
and closed the project (File->CloseProject). then C::B hangs and doesn't respond to anything,
all menu items are greyed out and you can't close it.

4.) then i ran C::B from gdb, first just running and closing, C::B exited normally,
the next time i opened a project and closed the project immediately - C::B hangs - no response to anything
from gdb i interrupted C::B by using C-c , and got then the backtrace.
attached is the gdb-log from this session.

HTH

ps. if i can test anything else, please post it here and explain what i've to do  :)

[attachment deleted by admin]

Der Meister:
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.

thomas:

--- Quote from: Der Meister on January 10, 2006, 10:44:00 pm ---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.

--- End quote ---
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.

tiwag:
with disabled Codecompletion-plugin i get this debug-report
when exiting C::B (File->Quit) after i previously had opened a project
and closed it by using (File->CloseProject).
(the same happens of course when i quit C::B without closing the project before)

the default.config file is not written and updated on the harddisk !




[attachment deleted by admin]

thomas:
Hmm.. that's funny. I see a  CloseActiveProject in there...

You know, just the other day, I said "I wonder why CloseActiveProject does not crash every time, since EditorManager is freed before ProjectManager, but since it's been working all that time, ok then...".

Maybe your problem will be gone after updating to the latest release (if you manage to compile it... I have a problem with the newest wxAUI update).
Everything regarding  Managers has been rewritten for better performance and stability, including the order of deallocation, which is now in order of dependence.

EDIT:
Revision 1707 compiles fine again :)
So... let's see if the bug has silently gone away... :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page