Author Topic: The 11 March 2007 build is out.  (Read 20766 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5193
The 11 March 2007 build is out.
« on: March 11, 2007, 08:39:03 pm »
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2.7z

To fix the menu alignment bug introduced in wx 2.6.3 [windows only bug] we have patched wx ourselves, and that results in the following alternative dll : http://prdownload.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2AndCbPatch_version3.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10.7z

For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26_gcc_cb_wx2.6.3p2.7z

The 11 March 2007 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20070311_rev3683_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20070311_rev3683_Ubuntu6.xx.deb (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20070311_rev3683_suse100-102.i586.rpm (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20070311_rev3683_fc4+5.i586.rpm (not yet)


Resolved Fixed:

  • Fixed debugging issue where the debugger would not jump to the breakpoint file/line when stopped for the first time (although it did stop and pressing F7 resumed debugging normally)
  • Added data breakpoints (experimental). Right click on a variable while debugging and choose "Add data breakpoint"
  • Console Wizard:
    * Added MSVC 8 (aka VC 2005) support.
    * Dropped Single-threaded CRT support for MSVC 7.1. Wizard now supports Multi-threaded Static/Dynamic CRT for MSVC 7.1 & 8.
    * Changed executable output path and small change in generated cpp code

Regressions/Confirmed/Annoying/Common bugs:

  • toolbar-images-not-changing-state (is a wx problem/Win XP problem)
  • menu items with icon not correctly aligned (since wx263) (is fixed with our special wx263/wx28 dll)


Offline Jewe

  • Multiple posting newcomer
  • *
  • Posts: 70
    • Fit Trainer
Re: The 11 March 2007 build is out.
« Reply #1 on: March 11, 2007, 08:54:58 pm »
Problems during starting of the program.
But the pop ups in the bottom right are blank.

Where can I get the information?

win2000
11 march version.

and yes, I removed the whole dir and then inserted everything from the web.

regards,

Jewe
Anything curved in the hardware can be straighten with software :D
OS: Vista64 + Debian(to play with)
Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

Offline nenin

  • Multiple posting newcomer
  • *
  • Posts: 95
Re: The 11 March 2007 build is out.
« Reply #2 on: March 11, 2007, 09:04:46 pm »
Same error, as with previous build:
ERROR: C:\bin\CodeBlocks/share/codeblocks/plugins/debugger.dll: not loaded (missing symbols?)

Offline Russell

  • Multiple posting newcomer
  • *
  • Posts: 30
Re: The 11 March 2007 build is out.
« Reply #3 on: March 11, 2007, 09:49:47 pm »
I usually just delete my entire share dir when I upgrade to a new nightly

Offline nenin

  • Multiple posting newcomer
  • *
  • Posts: 95
Re: The 11 March 2007 build is out.
« Reply #4 on: March 11, 2007, 09:57:38 pm »
I usually just delete my entire share dir when I upgrade to a new nightly
Yes... I did it two times today already. Last working build for me- cvn3677.  :(

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2180
Re: The 11 March 2007 build is out.
« Reply #5 on: March 11, 2007, 10:23:40 pm »
I usually just delete my entire share dir when I upgrade to a new nightly
Yes... I did it two times today already. Last working build for me- cvn3677.  :(

Then, most likely, you have an old codeblocks.dll sitting around that is being loaded by mistake. Either that, or an old debugger.dll is still being loaded.

Check your whole system for the following and make sure that the Nightly dll's have priority on the path. Else be sure that your current directory is the same as the one containing the CB executable and its dll's .

codeblocks.dll
exchndl.dll
mingwm10.dll
wxmsw26u_gcc_cb.dll
wxscintilla.dll
« Last Edit: March 12, 2007, 01:55:47 am by Pecan »

Offline cmb

  • Single posting newcomer
  • *
  • Posts: 6
Re: The 11 March 2007 build is out.
« Reply #6 on: March 12, 2007, 02:36:00 am »
May we have another ANSI build please? Apparently the last one was post by sethjackson on February 14, 2007. (http://forums.codeblocks.org/index.php/topic,5195.0.html) I have been having some problems with Code::Blocks starting and then hanging. The pop-up tells me that I should read the error messages but nothing is displayed after the splash screen. It is similar to Bug #10151 - Crash/hang when starting/exiting. Before I add to that report I'd like to try a version later than my SVN 3607.

Charles

Poobah

  • Guest
Re: The 11 March 2007 build is out.
« Reply #7 on: March 12, 2007, 04:06:43 am »
  • Added data breakpoints (experimental). Right click on a variable while debugging and choose "Add data breakpoint"

Thank you! Can users also manually add them (for use with array indices, etc.)?

Offline eckard_klotz

  • Almost regular
  • **
  • Posts: 150
Re: The 11 March 2007 build is out.
« Reply #8 on: March 12, 2007, 07:24:20 am »
Hello Everyone.

Quote
I have been having some problems with Code::Blocks starting and then hanging. The pop-up tells me that I should read the error messages but nothing is displayed after the splash screen.

This is the normal behaviour of the ansi-build because there are still some old dlls in the system which are replaced by new files in the current system .  You have to do a "clean-up" to make a ansi-build running.

Take a look to this discussion:

http://forums.codeblocks.org/index.php/topic,4937.0.html

Dear Sethjackson.

Did you never notice this problem on your system?

Best Regards,
                     Eckard Klotz.


Offline gd_on

  • Regular
  • ***
  • Posts: 494
Re: The 11 March 2007 build is out.
« Reply #9 on: March 12, 2007, 09:20:37 am »
Here too, problem with debugger.dll.
I have this message when loading codeblocks in a popup window at the right bottom :
One or more plugins were not loaded....
List of failed plugins :
debugger.dll.

I use this nightly with Win 2000. I have first deleted the whole share folder from the previous installation, and also all the files which are normally replaced in my codeblocks folder. I have also verified that there is not any remaining dlls anywhere on my PC. All are new, from this 7z file.

gd_on

PS : What is this sta00336 file within CodeBlocks\plugins ? (empty file)
« Last Edit: March 12, 2007, 09:29:08 am by 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 skirby

  • Almost regular
  • **
  • Posts: 137
Re: The 11 March 2007 build is out.
« Reply #10 on: March 12, 2007, 10:56:36 am »
Then, most likely, you have an old codeblocks.dll sitting around that is being loaded by mistake. Either that, or an old debugger.dll is still being loaded.

Check your whole system for the following and make sure that the Nightly dll's have priority on the path. Else be sure that your current directory is the same as the one containing the CB executable and its dll's .

codeblocks.dll
exchndl.dll
mingwm10.dll
wxmsw26u_gcc_cb.dll
wxscintilla.dll

I also deleted my share folder, verified that all files aboves are in root CodeBlocks directory and verified that I do not have any debugger.dll file elsewhere than in plugin directory but I always have error message when I launch Code::Blocks.

What's wrong?

Thanks and have a nice day.

Offline marfi

  • Multiple posting newcomer
  • *
  • Posts: 27
Re: The 11 March 2007 build is out.
« Reply #11 on: March 12, 2007, 11:06:00 am »
The debugger's behaviour is definitely better than in the previous version, but in some (unknown) cases is not possible to stop the debugging process (debugged application freezes) and also debugger's tooltips (evaluation of an object under a cursor) can cause the same problem... :(

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2180
Re: The 11 March 2007 build is out.
« Reply #12 on: March 12, 2007, 01:39:57 pm »
Here too, problem with debugger.dll.
I have this message when loading codeblocks in a popup window at the right bottom :
One or more plugins were not loaded....
List of failed plugins :
debugger.dll.

I use this nightly with Win 2000. I have first deleted the whole share folder from the previous installation, and also all the files which are normally replaced in my codeblocks folder. I have also verified that there is not any remaining dlls anywhere on my PC. All are new, from this 7z file.

gd_on

PS : What is this sta00336 file within CodeBlocks\plugins ? (empty file)

I just re-installed this nightly on XP. Here it is running the debugger with no load error. So the error must be caused by something external to CB.

Any chance you could update to an OS younger than 7 years?



Yes, there is indeed some stray zero length file in .../plugins.
Killerbot?
« Last Edit: March 12, 2007, 01:43:31 pm by Pecan »

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2180
Re: The 11 March 2007 build is out.
« Reply #13 on: March 12, 2007, 01:47:07 pm »
Same error, as with previous build:
ERROR: C:\bin\CodeBlocks/share/codeblocks/plugins/debugger.dll: not loaded (missing symbols?)

Oh, oh. I bet the older MSWindows has no DebugBreakProcess() support.
And that must be the missing symbol.

Edit: DebugBreakProcess is supported in dbgeng.dll and Kernel32.dll
So I suspect if you view/dump these dll's you won't find the following:

« Last Edit: March 12, 2007, 02:02:29 pm by Pecan »

Offline nenin

  • Multiple posting newcomer
  • *
  • Posts: 95
Re: The 11 March 2007 build is out.
« Reply #14 on: March 12, 2007, 02:26:52 pm »
Any chance you could update to an OS younger than 7 years?
When MS will produce anything better than Win2K, I will.  It definetely can not be XP.