how to get rid of contribs enabled ???

[tiwag]

i have serious problems with a C::B build on ubuntu 5.10 with contribs enabled.
every time when i close C::B, it crashes and can't save its configuration file default.conf

how do i get rid of contribs enabled

in the past i built C::B with
./configure --enable-contrib 


but now i want to revert this build option,

i tried:
./configure --disable-contrib 

i did a completely fresh svn-checkout, and after
./bootstrap
./configure

all contribs are build again ........ grrrrrrrrrrrrr     :x

where is this info stored, which file do i have to delete to get rid of these contribs enabled

any ideas?
thx

[Der Meister]

Are you really sure that the contrib-plugins are the reason for the crash? Did you disable them and tried again?
Anyway, could you run Code::Blocks within gdb to get a backtrace after the crash and post it here? I'm asking this because I got similar problems, but I'm not sure if it is a problem of Code::Blocks or of my system. Here is the thread where I reported this problem.
If your backtrace is similar to the one I reported I would assume that it is really a problem of Code::Blocks.

[thomas]

Are you using the very latest builds? A crash-on-close bug in EditorManager was fixed only 2 days ago.

[tiwag]

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,
when i tried to disable any or all plugins, C::B crashes when trying to save the default.conf.

that's the reason, why i want to build it completely without contribs plugins in order to test if it crashes then too

[tiwag]

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 

i have these ominous chrashes since the introduction of wxaui

[Urxae]

Did you try removing the respective shared libs from the plugins folder? They may not be rebuilt, just be left over from before.
make clean should also have worked (but probably not after a ./configure without --enable-contrib parameter)

[tiwag]

Did you try removing the respective shared libs from the plugins folder? They may not be rebuilt, just be left over from before.
make clean should also have worked (but probably not after a ./configure without --enable-contrib parameter)

i first tried with
make clean
sudo make uninstall

but then some libs were still left on the harddisk,

then i cleaned everything by hand in /usr/local/...
deleted my trunk directory and did a fresh svn checkout

then after
./bootstrap
./configure

the /src/plugins/contrib/Makefile and /src/plugins/contrib/Makefile.in and
their companions in the contribs subdirectories were generated too - so i was suspicious.

after
make
sudo make install

i found, that C::B was built without the contrib plugins. 

BUT - the  crashes are the same as before, 
attached is, what the Debug report "codeblocks" has generated ...

[attachment deleted by admin]

[tiwag]

now i ran C::B with gdb,

attached are the backtraces for

1.) just run CodeBlocks and exit by File->Quit
2.) run C::B, open a project and say File->Close Project

any ideas ??

[attachment deleted by admin]

[Der Meister]

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 

i have these ominous chrashes since the introduction of wxaui

I can confirm that, I have these crashes, too.

1.) just run CodeBlocks and exit by File->Quit
2.) run C::B, open a project and say File->Close Project

The 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.

Anyway, did the crash still occur if you modified your layout (so that Code::Blacks askes you if it should save the changes)?

[thomas]

wxApp::Yield() seems to appear quite a lot... let's hope this isn't a recursive Yield crash?  :?

Have you tried disabling code completion? It is the only one still using unsafe Yields.

[Der Meister]

The crash happend even with *no* plugin loaded. Thus I don't believe that code-completion is involved in this crash.

[thomas]

Think you could set a breakpoint into the first line of MainFrame::OnApplicationClose and then keep stepping into until the crash happens?

Should not take forever (maybe 100-200 steps), and might reveal the problem.

[Der Meister]

Well, I will test this, but you have to wait a bit. I don't have access to my linux-machine before friday afternoon.

[mandrav]

Could you update to 1702 and try again? I must have fixed it now.

[tiwag]

Could you update to 1702 and try again? I must have fixed it now.

test it soon - i'll report in approx. one hour ...