User forums > Help
Codeblocks is problems on Linux: Crashing all time, and others
namosca:
Hello!
I use CodeBlocks 16.01 on Lubuntu 16.10 (installed via apt-get install codeblocks).
1) I am having the following instabilty:
-While editing files, the program starts freezing every time more often (I can move the mouse but clicks has no effects). After some minutes, it crashes (sometimes with a warning from Linux, sometimes with no warning)
2) Other annoying behaviour:
-After selecting a syntax highlight theme (via settings -> editor -> syntax highlighting -> colour theme), if I quit codeblocks and open it again, the theme will be resetted to default
-They keyboard shortcut for swap source/header files is F11 in windows, but in Linux this key does other thing (going fullscreen). This unconsistent behaviour is very annoying.
This is all annoying and I am thinking of stop using CodeBlocks, but it would be a shame, because I use this program since a long time on Windows and have a good memory of it.
Which extra information do you need from me to be able to solve this problem?
Thank you!
oBFusCATed:
1. Just disable the symbol browser in the settings -> editor -> code completion
2. For me f11 works just fine. It is something coming from you window manager or gtk toolkit.
namosca:
Hi. I have tried this, but it still crashes.
Is there any log file I can provide so that you can better fix the problem?
oBFusCATed:
You can use gdb to get me a backtrace. Start gdb /path/to/codeblocks and when it crashes type thread apply all bt.
It is better to install any debuginfo packages before doing this step. Search your distro's documentation how to do it.
namosca:
Sorry, I never heard of debuginfo before, but reading https://wiki.ubuntu.com/Debug%20Symbol%20Packages, I am doing the following:
sudo apt-get install codeblocks-dbg
(gdb) file /usr/bin/codeblocks
(gdb) run
When the program crashes, I will do the command "thread apply all bt"
As I am not used to do this and I dont want to waste the crash when it happens (it takes time to happen and I dont want to miss it because I debugget it wrong), my question is:
Is this the correct way to get the information you need?
Thanks!
Navigation
[0] Message Index
[#] Next page
Go to full version