Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: kelaklub on September 28, 2006, 09:26:28 pm
-
I have been using codeblocks to work on a geometric library which I have attached to this post. The only change that I made to the CBP file was to change the target path to "..\ezGeom\ezGeom.exe". Regardless, this change was made a long time ago and it's been happy compiling ever since. The bug I have noticed goes like this...
- Click on the CBP file to launch the project.
- Simply exit codeblocks (Ctrl-Q).
- The Woah! dialog appears.
If I do something within codeblocks like displaying the About dialog or compiling my project and then exiting, it's all good. Has anyone else noticed this? I am using the Sept. 25 nightly build. Thanks.
[attachment deleted by admin]
-
Has anyone else noticed this?
Nope, works fine here. (Revision 2999).
With regards, Morten.
-
I know the culprit: code completion. :)
-
I know the culprit: code completion. :)
Dammed. I have to admit: Thomas is right. If I enable CC I get the crash. :-(
Anyway: No log file is produced? Why the f*** is this?!
-
I know the culprit: code completion. :)
I thought you were going to say KeyBinder. :)
-
spoiling your party, everythings works fine for me, all plug-ins enabled .....
Maybe my machine is fast enough to have already every job done before I can even do ctrl-q ??
-
Maybe my machine is fast enough to have already every job done before I can even do ctrl-q ??
Yes, most likely. I have to be *very* quick, too to achive the crash.
-
Hi
I have some similar issues on linux. As soon as I open a project, codeblocks window closes. I have an athlon64 dual core machine and I cannot use codeblocks when the codecompletion is enabled.(a good autocompletion is the thing I miss the most on linux). I know in my case the problem is linked with cairo (This bug is discussed a few times in the forum). Have you tried to start codeblocks from a console ? You might be able to see that 'codeblocks: /build/buildd/libcairo-1.2.2/src/cairo-ft-font.c:681: _cairo_ft_unscaled_font_set_scale: Assertion `error == 0' failed.
Aborted'
I cannot wait to see this bug fixed.