Author Topic: On start then immediate exit crash  (Read 3553 times)

Offline kelaklub

  • Multiple posting newcomer
  • *
  • Posts: 14
On start then immediate exit crash
« 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]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: On start then immediate exit crash
« Reply #1 on: September 28, 2006, 10:03:35 pm »
Has anyone else noticed this?
Nope, works fine here. (Revision 2999).
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: On start then immediate exit crash
« Reply #2 on: September 28, 2006, 10:10:05 pm »
I know the culprit: code completion. :)
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: On start then immediate exit crash
« Reply #3 on: September 28, 2006, 10:11:22 pm »
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?!
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2180
Re: On start then immediate exit crash
« Reply #4 on: September 28, 2006, 10:34:51 pm »
I know the culprit: code completion. :)

I thought you were going to say KeyBinder.  :)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5193
Re: On start then immediate exit crash
« Reply #5 on: September 28, 2006, 10:40:16 pm »
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 ??

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: On start then immediate exit crash
« Reply #6 on: September 28, 2006, 11:25:57 pm »
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.
« Last Edit: September 29, 2006, 01:50:05 pm by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline manowar

  • Multiple posting newcomer
  • *
  • Posts: 16
Re: On start then immediate exit crash
« Reply #7 on: September 29, 2006, 12:45:38 pm »
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.