Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on November 05, 2013, 11:38:00 pm

Title: The 05 November 2013 build (9435) is out.
Post by: killerbot on November 05, 2013, 11:38:00 pm
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works (http://forums.codeblocks.org/index.php/topic,3232.0.html).

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2812_gcc471-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc471-TDM.7z
And the exception handler dll (for better crash reports) : http://prdownload.berlios.de/codeblocks/exchndl_gcc471-TDM.7z

The 05 November 2013 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20131105_rev9435_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 05 November 2013 build (9435) is out.
Post by: dmoore on November 06, 2013, 05:19:11 am
Ubuntu packages (i386 + AMD64 for Precise through Trusty) are available here (https://code.launchpad.net/~damien-moore/+archive/codeblocks-nightly).

Code
sudo add-apt-repository ppa:damien-moore/codeblocks-nightly
sudo apt-get update
sudo apt-get install codeblocks codeblocks-contrib

Note: If you are using Code::Blocks from Pasgui's repository you will need to uninstall it and disable that repo before adding this one and reinstalling.

Workaround for possible crash related to compiler plugin at start up:
1. Open terminal, run "codeblocks --safe-mode"
2. Plugins -> Manage Plugins -> Compiler plugin -> Enable, then close the dialog
3. Accept all prompts
4. Close codeblocks
5. Start codeblocks as you normally would and everything should work normally.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: Jenna on November 06, 2013, 12:15:51 pm
As usual:
Debian packages (binaries and sources) for 32-bit and 64-bit systems (stable and testing) can be found in my debian-repo (http://apt.jenslody.de/).
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc18, fc19 and fc20) and RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) can be found in my rpm-repo (http://rpm.jenslody.de) .
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 07, 2013, 07:20:57 pm
first of all, sorry for reporting an older svn revision issue here which is newer, but since yesterday i have been dealing with peculiar behavior on my Debian machine with svn9423.

Below is the crashing report file that just got generated upon opening C::B.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: oBFusCATed on November 07, 2013, 07:36:30 pm
As far as I can see this log contains no useful information, so please install debug-symbols or rebuild with --enable-debug configure option.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 07, 2013, 08:05:59 pm
Quote from: oBFusCATed on November 07, 2013, 07:36:30 pm
As far as I can see this log contains no useful information, so please install debug-symbols or rebuild with --enable-debug configure option.

I can't compile the latest HEAD :/
Code
In file included from mozilla_chardet/src/nsBig5Prober.cpp:7:0:
../../src/include/mozilla_chardet/xpcom/glue/nsDebug.h:22:19: fatal error: prprf.h: No such file or directory
 #include "prprf.h"
                   ^
compilation terminated.
make[3]: *** [nsBig5Prober.lo] Error 1
make[3]: Leaving directory `/home/stefanos/svn_code/CodeBlocks/src/sdk'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/stefanos/svn_code/CodeBlocks/src/sdk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stefanos/svn_code/CodeBlocks/src'
make: *** [all-recursive] Error 1

UPDATE: LOL, I think it was a typo of mine during compilation procedure. Instead of placing the debug flag in bootstrap, I placed it in configure.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: stahta01 on November 07, 2013, 08:52:44 pm
@killerbot:

I created a patch that speeds up the time it takes to Compile wxContribItems.
I thought at first the use of a wxWidgets Precompiled Header was the cause of the speedup.
But, most of the speedup was because of the cb project changes needed to use the PCH.

I have tested the compiling of the wxContribItems project; but, I have not run-time tested any of it.

http://forums.codeblocks.org/index.php/topic,18523.msg126748.html#msg126748 (http://forums.codeblocks.org/index.php/topic,18523.msg126748.html#msg126748)

Tim S.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: oBFusCATed on November 07, 2013, 09:05:43 pm
Quote from: ToApolytoXaos on November 07, 2013, 08:05:59 pm
UPDATE: LOL, I think it was a typo of mine during compilation procedure. Instead of placing the debug flag in bootstrap, I placed it in configure.
No, it is not ---enable-debug is configure option, but it is broken at the moment.

But anyway, can you try using Jens' packages instead of self building? Self building causes tons of problems if one is not disciplined!
Title: Re: The 05 November 2013 build (9435) is out.
Post by: Jenna on November 07, 2013, 09:30:48 pm
Fixed in trunk, by undefining DEBUG in nsDebug.h, so we never try to use mozilla's debug-macros.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 07, 2013, 09:49:16 pm
Quote from: oBFusCATed on November 07, 2013, 09:05:43 pm
No, it is not ---enable-debug is configure option, but it is broken at the moment.
Well, believe it or not, with ./bootstrap --help, I saw that I could use it and used it and compiled just fine; time will tell if it's going to be behaving properly though.

Quote from: oBFusCATed on November 07, 2013, 09:05:43 pm
But anyway, can you try using Jens' packages instead of self building? Self building causes tons of problems if one is not disciplined!
I have no problems to build an entire machine from scratch! LOL :D I moved from a masochist world called FreeBSD to Debian and trust me, building a single project like Code::Blocks looks like a game comparing to the one-week compilation procedure on a hyperthreading PC with FreeBSD ports.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 07, 2013, 09:54:11 pm
Just a note by the way; I think there's an issue with curly brackets completion on both Windows and Linux.

For example, somebody try this on a Linux machine please:

Code
/* Here, highlight val until something; and press { */
if (something) val = something;

/* The code will look afterwards something like the following below: */
{
    if (something) val = something;
}

Now, on Windows it removes the highlighted line and replaces it with the curly brackets which obviously that's not the default behavior.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: Jenna on November 07, 2013, 10:00:52 pm
Quote from: ToApolytoXaos on November 07, 2013, 09:49:16 pm
Quote from: oBFusCATed on November 07, 2013, 09:05:43 pm
No, it is not ---enable-debug is configure option, but it is broken at the moment.
Well, believe it or not, with ./bootstrap --help, I saw that I could use it and used it and compiled just fine; time will tell if it's going to be behaving properly though.

I can't believe you, because the bootstrap-script does not take any arguments.
You can of course add what ever you want, but it's ignored.

--enable-debug is in fact a parameter of the configure-script, and it adds (among others) -DDEBUG to the Makefile's .
ANd this define was also used in mozilla's header.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 07, 2013, 10:30:20 pm
Quote from: jens on November 07, 2013, 10:00:52 pm
I can't believe you, because the bootstrap-script does not take any arguments.
You can of course add what ever you want, but it's ignored.

--enable-debug is in fact a parameter of the configure-script, and it adds (among others) -DDEBUG to the Makefile's .
ANd this define was also used in mozilla's header.

Well, indeed you were right. I literally screw things up. I built my system without debug -_-. I just ran through history commands and saw that it was in ./configure --help and not in ./bootstrap --help. I guess i'm too tired for today. I will fix it tomorrow.

Thank you jens for your clarification and for your patience.

cheers.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: MateusMP on November 08, 2013, 01:56:41 am
Hi,

I've been using Code Blocks for some time (a few years already...), and really like the program.
So, I'm here to support by reporting some bugs i found recently. (Not sure if they're bugs actually, but they seems like a strange behaviour for me).


Step by Step:
   Open Code Blocks.
   Create a new Project.
   Create a new virtual folder A, drag some files inside it.
   Create a new virtual folder B, drag some files inside it.
   Create a new virtual folder Parent.
   Select folder A, hold shift, click on the LAST file of folder B. Move the selection over the Parent folder.
   
Expected:
   Folders A and B are moved inside the Parent folder.

Problem:
   All the files will be moved inside the folder "Parent", but folder A will be empty and B folder will disappear.

OBS: Also, try this: put A and B inside Parent, and try to take them out following the same steps. All the files will be moved out of the folders, but neither A nor B will be destroyed.

---
Another Bug?:
Using the same project as the previous bug, change something on the project configuration (So it'll need to be saved, moving the files from virtual folders is enough), close Code Blocks.
-> 1º Dialog will ask if you want to save the Workspace, select No.
-> 2º Dialog will ask if you want to save changes to the project, select No.
-> 3º ANOTHER dialog will ask, again, if you want to save changes to the project.
Is that right? Maybe, just a double check?

Tested on 9425 and 9435.

Thanks!
Title: Re: The 05 November 2013 build (9435) is out.
Post by: Alpha on November 08, 2013, 02:05:01 am
Quote from: ToApolytoXaos on November 07, 2013, 09:54:11 pm
Just a note by the way; I think there's an issue with curly brackets completion on both Windows and Linux.
[...]
What do you have set for Settings->Editor->Selection brace completion ?
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 08, 2013, 07:24:27 am
Quote from: Alpha on November 08, 2013, 02:05:01 am
What do you have set for Settings->Editor->Selection brace completion ?
It was unckecked and checked it now; I have just tested it and the same issue that exists on Linux exists here as well (svn9435).

See it in action.

Before highlight:
(http://i40.tinypic.com/s1182r.png)

Highlighted:
(http://i42.tinypic.com/339k3o6.png)

Brackets applied:
(http://i41.tinypic.com/10olhnc.png)

Now, another interesting thing happens if you place it on the next line.

Next line:
(http://i41.tinypic.com/2wnvj4g.png)

Next line highlighted:
(http://i39.tinypic.com/2lwvjpt.png)

Next line curly brackets applied:
(http://i39.tinypic.com/213jkhd.png)
Title: Re: The 05 November 2013 build (9435) is out.
Post by: Alpha on November 08, 2013, 02:54:06 pm
Confirmed.  Unfortunately, it is not an easy problem (at least, not easy for me) to fix.  This behaviour is in SmartIndentCPP, which already contains a decent amount of convoluted logic and dark magic.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 08, 2013, 06:07:25 pm
Quote from: oBFusCATed on November 07, 2013, 07:36:30 pm
As far as I can see this log contains no useful information, so please install debug-symbols or rebuild with --enable-debug configure option.
Crash still exists even with the latest revision. You may find the report as an attachment.

Here's the issue demangled with c++filt:
Code
*** Error in `codeblocks': corrupted double-linked list: 0x0c6838b0 ***
======= Backtrace: =========
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x75e42)[0xb5adce42]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x782be)[0xb5adf2be]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_malloc+0x53)[0xb5ae03d3]
/usr/lib/i386-linux-gnu/libwx_baseu-2.8.so.0(wxStringBase::AllocBuffer(unsigned int)+0x44)[0xb68bd654]
/usr/lib/i386-linux-gnu/libwx_baseu-2.8.so.0(wxStringBase::AllocBeforeWrite(unsigned int)+0x38)[0xb68bd838]
/usr/lib/i386-linux-gnu/libwx_baseu-2.8.so.0(wxString::GetWriteBuf(unsigned int)+0x24)[0xb68bf854]
/usr/lib/i386-linux-gnu/libwx_baseu-2.8.so.0(wxString::FromAscii(char const*)+0xa4)[0xb68c0084]
/usr/lib/i386-linux-gnu/libwx_baseu-2.8.so.0(wxDynamicLibrary::ListLoaded()+0x15e)[0xb68e350e]
/usr/lib/i386-linux-gnu/libwx_gtk2u_qa-2.8.so.0(wxDebugReport::DoAddLoadedModules(wxXmlNode*)+0x22)[0xb6e40f32]
/usr/lib/i386-linux-gnu/libwx_gtk2u_qa-2.8.so.0(wxDebugReport::AddContext(wxDebugReport::Context)+0x45b)[0xb6e432db]
/usr/lib/i386-linux-gnu/libwx_gtk2u_qa-2.8.so.0(wxDebugReport::AddAll(wxDebugReport::Context)+0x17)[0xb6e44b37]
codeblocks[0x808b066]
/usr/lib/i386-linux-gnu/libwx_baseu-2.8.so.0(wxFatalSignalHandler+0x23)[0xb68fcd03]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xb776d400]
[0x99eaa8d]
Title: Re: The 05 November 2013 build (9435) is out.
Post by: oBFusCATed on November 08, 2013, 06:22:13 pm
Can you try with a package from Jens' repo?
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 08, 2013, 06:23:21 pm
OK, but i guess I should install it in a different location to avoid extra headaches.

UPDATE: Done so; still crashes. Time for uninstallation.

I just read your message below. Yes, I have uninstalled my version and now sees jens' version and work fine for now. Let's see how things will work from now on.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: oBFusCATed on November 08, 2013, 06:42:21 pm
No, first remove all artefacts from your self-built C::B that you have placed in /usr then install the packages.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 08, 2013, 07:15:39 pm
Custom AStyle does not work both on svn9435 and svn9438; I don't know if I'm doing something wrong, but when I edit the coding style i feel the most comfortable with, and use it on a project, nothing happens. As soon as I open "Source Formatter" from "Editor" settings, it's empty.

Is this behavior normal?
Title: Re: The 05 November 2013 build (9435) is out.
Post by: oBFusCATed on November 08, 2013, 08:08:53 pm
Quote from: ToApolytoXaos on November 08, 2013, 07:15:39 pm
Is this behavior normal?
Exact steps to reproduce please!
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 08, 2013, 10:49:17 pm
Go to Settings, Source Formatter, copy the sample code, go to Custom.

Edit the code to look something like the following below:

Code
int Foo(bool isBar) {
    if (isBar) {
        bar();
        return 1;
    }
    else
        return 0;
}
After you done so, press OK. Edit your code to look something like totally different than the style above; right click and choose Format use AStyle; nothing happens. Go back to Source Formatter; voilà! The Custom is empty.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 10, 2013, 09:59:06 pm
Quote from: oBFusCATed on November 08, 2013, 06:22:13 pm
Can you try with a package from Jens' repo?
Crashing insists even with jens' packages.

Code
<stack>
    <frame level="0" function="wxFatalSignalHandler" offset="00000023"/>
    <frame level="1" function="__kernel_sigreturn" offset="00000000"/>
    <frame level="2" function="wxFrame::OnInternalIdle()" offset="00000026"/>
    <frame level="3" function="wxAppBase::SendIdleEvents(wxWindow*, wxIdleEvent&amp;)" offset="00000029"/>
    <frame level="4" function="wxAppBase::ProcessIdle()" offset="0000007e"/>
    <frame level="5"/>
    <frame level="6"/>
    <frame level="7" function="g_main_context_dispatch" offset="0000013e"/>
    <frame level="8"/>
    <frame level="9" function="g_main_loop_run" offset="0000007b"/>
    <frame level="10" function="gtk_main" offset="000000b0"/>
    <frame level="11" function="wxEventLoop::Run()" offset="0000003e"/>
    <frame level="12" function="wxAppBase::MainLoop()" offset="0000004f"/>
    <frame level="13" function="wxAppBase::OnRun()" offset="0000001f"/>
    <frame level="14" function="CodeBlocksApp::OnRun()" offset="00000000" file="/tmp/buildd/codeblocks-12.11svn9435/src/src/app.cpp" line="811"/>
  </stack>
Title: Re: The 05 November 2013 build (9435) is out.
Post by: oBFusCATed on November 10, 2013, 10:15:14 pm
What is the ouptut of ldd /usr/bin/codeblocks?
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 10, 2013, 10:20:46 pm
Quote from: oBFusCATed on November 10, 2013, 10:15:14 pm
What is the ouptut of ldd /usr/bin/codeblocks?

Code
linux-gate.so.1 (0xb7751000)
libcodeblocks.so.0 => /usr/lib/libcodeblocks.so.0 (0xb70e0000)
libwx_gtk2u_richtext-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_gtk2u_richtext-2.8.so.0 (0xb6ffa000)
libwx_gtk2u_aui-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_gtk2u_aui-2.8.so.0 (0xb6f98000)
libwx_gtk2u_xrc-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_gtk2u_xrc-2.8.so.0 (0xb6f0c000)
libwx_gtk2u_qa-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_gtk2u_qa-2.8.so.0 (0xb6eef000)
libwx_gtk2u_html-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_gtk2u_html-2.8.so.0 (0xb6e57000)
libwx_gtk2u_adv-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-2.8.so.0 (0xb6d9e000)
libwx_gtk2u_core-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_gtk2u_core-2.8.so.0 (0xb6a59000)
libwx_baseu_xml-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_baseu_xml-2.8.so.0 (0xb6a4f000)
libwx_baseu_net-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_baseu_net-2.8.so.0 (0xb6a23000)
libwx_baseu-2.8.so.0 => /usr/lib/i386-linux-gnu/libwx_baseu-2.8.so.0 (0xb68d7000)
libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 (0xb6469000)
libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 (0xb63ba000)
libatk-1.0.so.0 => /usr/lib/i386-linux-gnu/libatk-1.0.so.0 (0xb6398000)
libgio-2.0.so.0 => /usr/lib/i386-linux-gnu/libgio-2.0.so.0 (0xb622f000)
libpangoft2-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0 (0xb6219000)
libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 (0xb620c000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0 (0xb61e9000)
libcairo.so.2 => /usr/lib/i386-linux-gnu/libcairo.so.2 (0xb60b0000)
libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 (0xb6064000)
libfreetype.so.6 => /usr/lib/i386-linux-gnu/libfreetype.so.6 (0xb5fc8000)
libfontconfig.so.1 => /usr/lib/i386-linux-gnu/libfontconfig.so.1 (0xb5f8d000)
libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 (0xb5f3b000)
libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb5e38000)
libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb5e1d000)
libdl.so.2 => /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb5e18000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb5d2f000)
libm.so.6 => /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb5ceb000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb5ccf000)
libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb5b20000)
libgthread-2.0.so.0 => /usr/lib/i386-linux-gnu/libgthread-2.0.so.0 (0xb5b1d000)
libXinerama.so.1 => /usr/lib/i386-linux-gnu/libXinerama.so.1 (0xb5b19000)
libXxf86vm.so.1 => /usr/lib/i386-linux-gnu/libXxf86vm.so.1 (0xb5b12000)
libSM.so.6 => /usr/lib/i386-linux-gnu/libSM.so.6 (0xb5b0a000)
libpng12.so.0 => /lib/i386-linux-gnu/libpng12.so.0 (0xb5ae0000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb5ac7000)
libjpeg.so.8 => /usr/lib/i386-linux-gnu/libjpeg.so.8 (0xb5a8e000)
libtiff.so.5 => /usr/lib/i386-linux-gnu/libtiff.so.5 (0xb5a19000)
libexpat.so.1 => /lib/i386-linux-gnu/libexpat.so.1 (0xb59f1000)
libgmodule-2.0.so.0 => /usr/lib/i386-linux-gnu/libgmodule-2.0.so.0 (0xb59ec000)
libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xb58b3000)
libXcomposite.so.1 => /usr/lib/i386-linux-gnu/libXcomposite.so.1 (0xb58af000)
libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xb58ab000)
libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xb58a5000)
libXrender.so.1 => /usr/lib/i386-linux-gnu/libXrender.so.1 (0xb589b000)
libXi.so.6 => /usr/lib/i386-linux-gnu/libXi.so.6 (0xb588a000)
libXrandr.so.2 => /usr/lib/i386-linux-gnu/libXrandr.so.2 (0xb587f000)
libXcursor.so.1 => /usr/lib/i386-linux-gnu/libXcursor.so.1 (0xb5873000)
libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xb5861000)
libselinux.so.1 => /lib/i386-linux-gnu/libselinux.so.1 (0xb583f000)
libresolv.so.2 => /lib/i386-linux-gnu/i686/cmov/libresolv.so.2 (0xb5827000)
libharfbuzz.so.0 => /usr/lib/i386-linux-gnu/libharfbuzz.so.0 (0xb57d3000)
libpixman-1.so.0 => /usr/lib/i386-linux-gnu/libpixman-1.so.0 (0xb5725000)
libEGL.so.1 => /usr/lib/i386-linux-gnu/libEGL.so.1 (0xb5703000)
libxcb-shm.so.0 => /usr/lib/i386-linux-gnu/libxcb-shm.so.0 (0xb56ff000)
libxcb-render.so.0 => /usr/lib/i386-linux-gnu/libxcb-render.so.0 (0xb56f4000)
libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xb56d2000)
libGL.so.1 => /usr/lib/i386-linux-gnu/libGL.so.1 (0xb5679000)
librt.so.1 => /lib/i386-linux-gnu/i686/cmov/librt.so.1 (0xb5670000)
libthai.so.0 => /usr/lib/i386-linux-gnu/libthai.so.0 (0xb5666000)
libffi.so.6 => /usr/lib/i386-linux-gnu/libffi.so.6 (0xb565e000)
libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xb561f000)
/lib/ld-linux.so.2 (0xb7752000)
libICE.so.6 => /usr/lib/i386-linux-gnu/libICE.so.6 (0xb5606000)
libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xb5600000)
liblzma.so.5 => /lib/i386-linux-gnu/liblzma.so.5 (0xb55d9000)
libjbig.so.0 => /usr/lib/i386-linux-gnu/libjbig.so.0 (0xb55ca000)
libgraphite2.so.3 => /usr/lib/i386-linux-gnu/libgraphite2.so.3 (0xb55af000)
libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xb55ac000)
libxcb-dri2.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri2.so.0 (0xb55a6000)
libxcb-xfixes.so.0 => /usr/lib/i386-linux-gnu/libxcb-xfixes.so.0 (0xb559d000)
libxcb-shape.so.0 => /usr/lib/i386-linux-gnu/libxcb-shape.so.0 (0xb5599000)
libwayland-client.so.0 => /usr/lib/i386-linux-gnu/libwayland-client.so.0 (0xb558d000)
libwayland-server.so.0 => /usr/lib/i386-linux-gnu/libwayland-server.so.0 (0xb557e000)
libgbm.so.1 => /usr/lib/i386-linux-gnu/libgbm.so.1 (0xb5576000)
libudev.so.1 => /lib/i386-linux-gnu/libudev.so.1 (0xb5562000)
libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xb5555000)
libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xb5551000)
libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xb554b000)
libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xb5534000)
libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xb551b000)
libdatrie.so.1 => /usr/lib/i386-linux-gnu/libdatrie.so.1 (0xb5512000)
Title: Re: The 05 November 2013 build (9435) is out.
Post by: oBFusCATed on November 10, 2013, 10:27:10 pm
Hm, can you run successfully any wxGTK app on this machine - Filezilla, Audacity, Amule, xchm, etc?
Title: Re: The 05 November 2013 build (9435) is out.
Post by: ToApolytoXaos on November 10, 2013, 10:30:09 pm
Yes, I just used aegisub to edit some subs (lol), and i have been using Audacity for ages without any problem.
Title: Re: The 05 November 2013 build (9435) is out.
Post by: Bat on November 16, 2013, 08:31:29 pm
Quote from: MateusMP on November 08, 2013, 01:56:41 am
Another Bug?:
Using the same project as the previous bug, change something on the project configuration (So it'll need to be saved, moving the files from virtual folders is enough), close Code Blocks.
-> 1º Dialog will ask if you want to save the Workspace, select No.
-> 2º Dialog will ask if you want to save changes to the project, select No.
-> 3º ANOTHER dialog will ask, again, if you want to save changes to the project.
Is that right? Maybe, just a double check?

Tested on 9425 and 9435.

Thanks!

I think this patch I've sended correct this behaviour
https://developer.berlios.de/patch/?func=detailpatch&patch_id=3523&group_id=5358