As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
It is pretty normal, most of the time there is a bug in you program... use the debugger to find it...
Do NOT try to add MSVC Libraries to your MinGW Debug Build.
Quote from: stahta01 on April 16, 2011, 02:25:29 amDo NOT try to add MSVC Libraries to your MinGW Debug Build.i didn't use MSVC lib. by the way, my program is normal either in debug or release within VS2005.
Quote from: facat on April 16, 2011, 02:33:28 amQuote from: stahta01 on April 16, 2011, 02:25:29 amDo NOT try to add MSVC Libraries to your MinGW Debug Build.i didn't use MSVC lib. by the way, my program is normal either in debug or release within VS2005.Then why did you do so in the zipped project file.Edit: If you do not believe me; just turn on Full Compiler Logging and look at the g++ linker command and you will see the .lib file trying to be linked on debug build.http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3FTim S.
when i tick "Optimize more( for speed [-O1])" in debug project, the result is the same the a release one.
Quote from: facat on April 16, 2011, 07:51:43 amwhen i tick "Optimize more( for speed [-O1])" in debug project, the result is the same the a release one.mostly(probably)1, this is a compiler bug, which produce different target code and different behavior.2, some lib conflict. e.g. you app use a debug version CRT, then your lib use some release version CRT, then this will cause some error.The important is: all these kind of bug is not related to Codeblocks, Codeblocks is only an IDE, and we give a convenient programming environment.
i prone to regard it as a compile bug. can i update the gcc in my Code Block to a higher version, and how?
The only way to be sure it is a compiler bug, is to check the assembly.But I'm pretty sure you have a bug in you code, you just have to find it