Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on May 24, 2006, 08:57:00 pm

Title: The 24 May 2006 build is out.
Post by: killerbot on May 24, 2006, 08:57:00 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://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z

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://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z

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

The 24 May 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060524_rev2499_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060524_rev2499.deb
         http://download.berlios.de/codeblocks/CB_20060524_rev2499_fc4+5.rpm


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 24 May 2006 build is out.
Post by: delux on May 25, 2006, 08:19:05 am
There is still problem with gdb output parsing in watches window.
Example attached.

[attachment deleted by admin]
Title: Re: The 24 May 2006 build is out.
Post by: MortenMacFly on May 25, 2006, 08:35:06 am
Example attached.
...please read that: http://forums.codeblocks.org/index.php?topic=3186.0 (http://forums.codeblocks.org/index.php?topic=3186.0) topic. It came out of your first post. Please try what happens if you set the file encoding to UTF-8 (Settings -> Editor -> General settings -> "Default Encoding when opening files"...?!
With regards, Morten.

Edit: ...or do you mean the trailing '{' (I can see the value properly in your example)?
Title: Re: The 24 May 2006 build is out.
Post by: mandrav on May 25, 2006, 10:50:06 am
There is still problem with gdb output parsing in watches window.
Example attached.

There is no problem with gdb output parsing. There's problem with gdb's output and we can't do much about it ;)

Code
> output *ptr 
{char_var = -83 'ar = 123}

EDIT: Actually, it's the way gdb's output is converted to wxString. Let me look into this...
Title: Re: The 24 May 2006 build is out.
Post by: mandrav on May 25, 2006, 11:02:47 am
OK, I 've found the cause in sdk/pipedprocess.cpp. The text stream we 're reading there, is using UTF8 conversion which is clearly the problem here.
I 've updated it to use the local system encoding, which hopefully will work fine. Worked fine for me in my tests. But please test watching vars as much as possible. Test compiling too. We wouldn't want to break what already works ;)
Also, Morten, please check your test file again and tell us if it works now...
Title: Re: The 24 May 2006 build is out.
Post by: MortenMacFly on May 25, 2006, 11:48:29 am
OK, I 've found the cause in sdk/pipedprocess.cpp. The text stream we 're reading there, is using UTF8 conversion which is clearly the problem here.
I couldn't stand to point to: http://forums.codeblocks.org/index.php?topic=2910.msg22996#msg22996 (http://forums.codeblocks.org/index.php?topic=2910.msg22996#msg22996). It seems I haven't been so much wrong there... suprisingly... ;-)

Also, Morten, please check your test file again and tell us if it works now...
Fantastic! This fixes the issue with "Hähä"!!! :D :D :D ;-)

It seems today you are fixing really quite some nasty bugs - another success story. Good work!

Morten.

Ps.: Anyway: On my way to compile the new revision I got another crash. What I did was:
- Open C::B
- Open my C::B workspace (the C::B project plus all contrib plugins)
- Changing to Firefox and doing some reading while the workspace was loading
- Then... suddenly... in the background C::B crashed.
Please find the report file attached.

Pps.: I'm off for the rest of the weekend in case you wonder why it's getting silent... ;-)

[attachment deleted by admin]
Title: Re: The 24 May 2006 build is out.
Post by: chrisb on May 25, 2006, 12:12:05 pm
Test compiling too. We wouldn't want to break what already works ;)
Hey.

I've updated codeblocks to rev2502 right now and noticed that a problem occurred compiling the new pipedprocess.cpp.
The compiler complained that no proper constructor was found.

After checking the file, I found out that you do not deal the case if there's no wx-Unicode support.
So i discover the rest of the file and write a short patch for it. It there's no support the "old" constructor will be invoked.

Consider it:
Code
--- src/sdk/pipedprocess_old.cpp	2006-05-25 11:59:27.000000000 +0200
+++ src/sdk/pipedprocess.cpp 2006-05-25 12:02:06.000000000 +0200
@@ -174,7 +174,11 @@ bool PipedProcess::HasInput()
 
     if (IsErrorAvailable())
     {
-        cbTextInputStream serr(*GetErrorStream(), wxT(" \t"), wxConvLocal);
+        #if wxUSE_UNICODE
+        cbTextInputStream serr(*GetInputStream(), wxT(" \t"), wxConvLocal);
+        #else
+        cbTextInputStream serr(*GetErrorStream());
+        #endif
 
         wxString msg;
         msg << serr.ReadLine();
@@ -189,7 +193,11 @@ bool PipedProcess::HasInput()
 
     if (IsInputAvailable())
     {
+        #if wxUSE_UNICODE
         cbTextInputStream sout(*GetInputStream(), wxT(" \t"), wxConvLocal);
+        #else
+        cbTextInputStream sout(*GetErrorStream());
+        #endif
 
         wxString msg;
         msg << sout.ReadLine();
Title: Re: The 24 May 2006 build is out.
Post by: MortenMacFly on May 25, 2006, 12:12:23 pm
Also, Morten, please check your test file again and tell us if it works now...
I'm sorry to say this, but while working on that topic I found another two debugger issues that I have posted in a new thread because they are not related to this one. Please have a look here:
http://forums.codeblocks.org/index.php?topic=3197.0 (http://forums.codeblocks.org/index.php?topic=3197.0). :( :( :(
With best regards, Morten.
Title: Re: The 24 May 2006 build is out.
Post by: mandrav on May 25, 2006, 12:16:06 pm
Also, Morten, please check your test file again and tell us if it works now...
I'm sorry to say this, but while working on that topic I found another two debugger issues that I have posted in a new thread because they are not related to this one. Please have a look here:
http://forums.codeblocks.org/index.php?topic=3197.0 (http://forums.codeblocks.org/index.php?topic=3197.0). :( :( :(
With best regards, Morten.


Well, they 're irrelevant to the issues tracked here, so it's good that you found them :)
Title: Re: The 24 May 2006 build is out.
Post by: mandrav on May 25, 2006, 12:19:06 pm
Test compiling too. We wouldn't want to break what already works ;)
Hey.

I've updated codeblocks to rev2502 right now and noticed that a problem occurred compiling the new pipedprocess.cpp.
The compiler complained that no proper constructor was found.

After checking the file, I found out that you do not deal the case if there's no wx-Unicode support.
So i discover the rest of the file and write a short patch for it. It there's no support the "old" constructor will be invoked.

Thanks :)
I won't use your patch (there's an easier way to fix this), but thanks for pointing out the isuue.
Title: Re: The 24 May 2006 build is out.
Post by: lfm on May 26, 2006, 01:17:11 am
Code
> output *ptr 
{char_var = -83 'ar = 123}

EDIT: Actually, it's the way gdb's output is converted to wxString. Let me look into this...

The problem still exist. Using rev 2509 in chinese WinXP-sp2, open file encoding is windows-936, also tested utf-8.