User forums > Using Code::Blocks

Crash on KDE4 with enabled desktop effects when moving panes

(1/1)

dk:
Hello!

I've found a very annoying bug in the Code::Blocks, it is always crashes, when moving panes (such as "Management") to the docking position.

After a lot of investigation (see here and here) I've found a final reason: Code::blocks crashes when running under KDE-4 with enabled desktop effects.

Bug is reproducible at my system (ALT Linux + C::B nightly) and at Kubuntu 9.04 + C::B 8.02 from Ubuntu universe repository.

I think, this bug is on all modern systems with KDE-4.

Bug report: http://developer.berlios.de/bugs/?func=detailbug&bug_id=16296&group_id=5358

killerbot:
I have had similar experiences.

Sometimes editors become unlinked (that is 2 editor screens) (some mouse/keyboard combinations not willingly executed caused this). Then I try to drag them all together, and yes also ALWAYS crash.

MortenMacFly:

--- Quote from: dk on September 22, 2009, 04:23:12 pm ---I've found a very annoying bug in the Code::Blocks, it is always crashes, when moving panes (such as "Management") to the docking position.

--- End quote ---
Could you please try with a nightly? Because the "docking engine" is kind of completely new since we move to wxAUI completely.

dk:

--- Quote from: MortenMacFly on September 22, 2009, 05:25:39 pm ---I've found a very annoying bug in the Code::Blocks, it is always crashes, when moving panes (such as "Management") to the docking position.

--- End quote ---

I am using nightly builds on my linux distribution (ALT Linux 5.0), and there are crashes.

I've tested ubuntu and C::B 8.02 to be sure, that it isn't distro-specific bug.

Jenna:
I just installed kde4 on my development system.

I can confirm this crash, but only if composite is enabled.

It's really hard to track down, because if the crash occurs, the program ends and no backtrace is available, if I run the program with --sync, I am not able to make it crash.

It's most likely a wxWidgets or xorg bug and not a C::B bug, but unless we see where it really crashes it will be nearly impossible to solve.

Navigation

[0] Message Index