Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: johnpuppa on March 31, 2016, 11:36:01 pm
-
I'm experiencing repetitive crashes when using codeblocks 16.01 on debian amd64. I had the same problem on i386 too.
I tried to seek help also on another debian forum.
Here is the link of the discussion.
http://forums.debian.net/viewtopic.php?f=10&t=127620 (http://forums.debian.net/viewtopic.php?f=10&t=127620)
Release 16.01 rev 10692 (2016-01-23 15:52:29) gcc 5.3.1 Linux/unicode - 64 bit
Before I was using testing. Now I have update to stretch, but with no improvements.
On other distros it works fine, but on this machine I have no luck.
Hope you guys can help me.
-
Yes, most probably you need to disable the symbol browser in the code completion settings.
Debian has only wxgtk 3.0 and the symbol browser is known to cause problems in this version.
-
Yes, most probably you need to disable the symbol browser in the code completion settings.
Debian has only wxgtk 3.0 and the symbol browser is known to cause problems in this version.
Thanks, I will give it a go.. is there any chance to install wxgtk-2.8 that you know? the symbol browser is quite useful :)
-
Yes, most probably you need to disable the symbol browser in the code completion settings.
Debian has only wxgtk 3.0 and the symbol browser is known to cause problems in this version.
Thanks, I will give it a go.. is there any chance to install wxgtk-2.8 that you know? the symbol browser is quite useful :)
Yes, if you know how to build a Debian source package then; you can install wxgtk-2.8.
I forgot if I built Code::Blocks from source or from a Debian source package after installing wxgtk-2.8.
I did this about 6 months ago; so, it is possible that a few new issues might exist, now.
I did NOT test much of Code::Blocks other than the Compiler Plugin.
Tim S.
-
Yes, most probably you need to disable the symbol browser in the code completion settings.
Debian has only wxgtk 3.0 and the symbol browser is known to cause problems in this version.
Maybe someone should disable compiling (or at least disable access to it) the symbol browser if wxGtk3.0 is detected as a short-term solution ?
You can't tell it to be stable when it's not on some platforms...
Yves
-
I've thought about disabling it for all wx3.0 builds, but Morten has been working on a solution to the problem, so I wanted to wait a bit.
@Morten: Are you close to a solution? If not and you don't have time I can take over this task.
-
@Morten: Are you close to a solution? If not and you don't have time I can take over this task.
unfortunately not. The idea I had in mind with sending UI updates through an event and then running from the main thread do not work either. So this really needs major re-factoring.
-
Can you share a patch, so I can see what it doesn't work? :)
-
Can you share a patch, so I can see what it doesn't work? :)
I've reverted it some time ago because it was not working and made constantly CC crash.
As far as I can remember I made a public function "BuildTree" in the builder thread and instead of calling it directly in the thread I sent an event to the parent. The parent was then calling the public function. Would have been nice if it worked but it didn't and made things even worse.
-
this is my pain too,ubuntu fedora still have wx2.8,start with debian 8 had drop wx2.8