User forums > General (but related to Code::Blocks)

Release compiler?

(1/2) > >>

ninja9578:
Sometimes when testing, a program goes into an infinite loop and I have to kill it.  First I try the little red X on the top of Code::Blocks.  It says Aborting process 0... Be patient, but doesn't do anything, so after a few minutes I kill it using the task manager. 

Is there a way for me to tell Code::Blocks that I took care of the process and to stop trying to abort?  Because I have to shut down Code::Blocks and restart it so that I can compile again.  This is very annoying to me because I often have 5-10 projects open at the same time.

oBFusCATed:
Have you tried a recent nightly?

p.s. Things you have forgotten to tell us: c::b version, gcc version, os version...

ninja9578:
8.0.2,  Windows 7, and how can I tell what version of GCC I'm using?  I would assume 4.0 because iostreams work and they're broken in 4.2.  It's actually MinGW, not GCC.  I didn't upgrade it, I left it with the version that came with the IDE.

I don't do nightly builds, I learn my lesson with that using wxWidgets.

stahta01:

--- Quote from: ninja9578 on March 09, 2010, 08:24:59 pm ---8.0.2,  Windows 7, and how can I tell what version of GCC I'm using?  I would assume 4.0 because iostreams work and they're broken in 4.2.  It's actually MinGW, not GCC.  I didn't upgrade it, I left it with the version that came with the IDE.

I don't do nightly builds, I learn my lesson with that using wxWidgets.

--- End quote ---

The version packaged with the IDE IS NOT Vista Compatible; therefore it is unlikely to work with Windows 7.

The below should give the version of MinGW GCC you need 4.x or 3.4.5 ... R3 or higher.

--- Code: ---gcc -v

--- End code ---

ninja9578:
Thank you.  I have 3.4.5 (mingw-vista special)

Navigation

[0] Message Index

[#] Next page

Go to full version