Author Topic: The 02 November 2007 build (4592) is out.  (Read 21602 times)

Offline TDragon

  • Lives here!
  • ****
  • Posts: 936
    • Twilight Dragon Media
Re: The 02 November 2007 build (4592) is out.
« Reply #15 on: November 04, 2007, 03:35:02 pm »
Nope, this is a bug in certain versions of windres. Wipe your 4.2.1 installation directory and reinstall with MinGW's binutils-2.17.50-20060824-1 package.
http://tdm-gcc.tdragon.net/ - TDM-GCC compiler suite for Windows (GCC 5.1.0 2015-06-28, 32/64-bit, no extra DLLs)

Offline doomleika

  • Single posting newcomer
  • *
  • Posts: 3
Re: The 02 November 2007 build (4592) is out.
« Reply #16 on: November 04, 2007, 03:58:04 pm »
However, I mean when you "stepped into the scope" the watch still displays wrong number. i.e.when stepped on function "int lol()" call, it's wrong number, when stepped on ++k, it still wrong number, so does k =34; std::cout << k;.........well but the "cout" still produce the correct result. That's why I suspect the watch is broken in some way.....

Nah, it's not a bug. ^^
++k is resolved after the debugger stopped there, that's the reason why it shows the false number.
If you would put a breakpoint the line after, it should show correct output.

You'll find the same behaviour in Microsofts Visual Studio, if I remember right.
again, thx for reply.

Well, it doesn't. If you put a breakpoint at int main() or {, in MSVC 2005 EE, the locale watch doen't even show the variable k util you stepped in the scope, it will display the random number before the variable initialization statment, and after the initialization, it works fine. If you force put on a watch manually it will say "CXX0069: Error: variable needs stack frame" before the scope.

If it is not a "bug", at least the IDE should stop user putting a breakpoint at main() or {.
« Last Edit: November 04, 2007, 03:59:47 pm by doomleika »

Offline gd_on

  • Regular
  • ***
  • Posts: 494
Re: The 02 November 2007 build (4592) is out.
« Reply #17 on: November 04, 2007, 05:10:18 pm »
Thanks TDragon.
I had effectively a bad windres version (though it was from a binutils-2.17.50 but not the same date !!!).
Now it's OK. It compiles and the dll runs with C::B. Just one thing, my dll is 2.7 MO bigger than the one provided by killerbot. May be, he has stripped it.

gd_on
Windows 10, svn C::B (last version or almost!), WxWidgets 3.1.3, Compilers 8.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\MinGW64) or 32 bits (sjlj, posix in C:\MinGW32).

Offline ASJ

  • Multiple posting newcomer
  • *
  • Posts: 46
Re: The 02 November 2007 build (4592) is out.
« Reply #18 on: November 04, 2007, 09:46:32 pm »
Many, MANY thanks for fixing the "always rebuild all" bug! The problem is gone now and it is saving me a lot of time!
Thanks! :D :D :D

Offline pasgui

  • Almost regular
  • **
  • Posts: 165
    • LGP
Re: The 02 November 2007 build (4592) is out.
« Reply #19 on: November 04, 2007, 10:03:10 pm »
Build for Ubuntu i386/amd64 can be found here

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6671
    • My Best Post
Re: The 02 November 2007 build (4592) is out.
« Reply #20 on: November 04, 2007, 10:29:52 pm »
Just one thing, my dll is 2.7 MO bigger than the one provided by killerbot. May be, he has stripped it.

Yes, he almost always strips the DLL.

Tim S
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org