User forums > Using Code::Blocks

Advice on Version for Ubuntu

(1/3) > >>

tigerbeard:
After getting started with the CB 16.01 in Ubuntu 16.04LTS I am getting constant crashed in all sort of situations. Its a bit of a surprise, since on Windows I can not recall a single crash of C::B in many years.

I hope there are a lot of people out there using CodeBlocks in Linux (including Ubuntu), so you maybe someone could give me their experience on what version their regards as the most stable to use.

thanks

oBFusCATed:
The latest and greatest. 16.01 is full of crashes especially on ubuntu, which have been identified and fixed for 17.12.
I've posted patches for many crashes with 16.01 on launchpad, you can check with ubuntu's developers if they've been applied or not.
But generally it is better to just update (if you cannot find packages, just build them yourself).

One major source of crashes is the symbol browser. If you disable it the frequency would lower, but there are others.

tigerbeard:
Great, thanks that is very helpful info not continue to wast time on 16.01 versions.

Before reading you reply I just installed 17.02. I am sorry to say that, but I find it unusable, because you seem to have totally disabled the symbol browser.  I thought from the release notes its just deactivated by default. I must add that the SB actually is the killer feature of C::B for me and I am totally lost without it (even more with this huge tree leaf spacing).

Interesting to learn that its troubles (using thread gui code etc.) are causing so much worse trouble than in windows, where it often hangs but it never crahed on me. Is there any (dirty) way to get the symbol browser enabled because I'd love to check out the 17.12 official?

If not, do I have the chance to get it enabled in the nightlies?

BlueHazzard:

--- Quote ---s there any (dirty) way to get the symbol browser enabled because I'd love to check out the 17.12 official?
--- End quote ---
If you activate the symbol browser you will get the crashes. The only solution is to rewrite the whole part of codeblocks, but there is no dev who is willing to do it (help is needed)

One possible solution is to compile codeblocks by yourself but with wxWidgets 2.8.X instead of the official wxWidgets 3.X.X of your ubuntu distribution. This should be possible and it should work without crashing....

tigerbeard:

--- Quote ---If you activate the symbol browser you will get the crashes.
--- End quote ---
I am aware of that.
But that does not mean its not useful. Example. try to look at foreign code with 20.000Loc with SB or with File view only. The file view does not tell you anything about how large the classes are, public/private functions, member vars name space structure, name it. And when i have 1hr to check out such a  project, I'd still do it with a CB crahing on me 10times in that time, rather than doing it without a symbol browser.
 

--- Quote ---The only solution is to rewrite the whole part of codeblocks, but there is no dev who is willing to do it (help is needed)

--- End quote ---
I can fully understand its hard to to such a rewrite in open source. The use case above would benefit from a "lock" button to quickly enable/disable it until its being eventually fixed. Just an example of an other "solution".


--- Quote ---One possible solution is to compile codeblocks by yourself but with wxWidgets 2.8.X instead of the official wxWidgets 3.X.X of your ubuntu distribution. This should be possible and it should work without crashing..
--- End quote ---
Cool. Although I guess this implies the nightlies also do lock the SB feature.

If compiling CB 17.12 with 2.8 is an option that a good way out indeed. I had thought that I did read somewhere that wx3.xx is a requirement for 17.12 and it would not compile, but maybe I misunderstood that.

So if when I did compile it with 2.8, how would I enable the SB then? Woudn't it still be locked?

Navigation

[0] Message Index

[#] Next page