User forums > Nightly builds

The 13 April 2009 build (5535) is out.

<< < (4/11) > >>

ollydbg:
@dk.
In my windows system, I always get crash when I drag the toolbar.
See my post here, Is it related issue?
http://forums.codeblocks.org/index.php/topic,9648.msg67823.html#msg67823

Someone suggests using a old wxWidgets library. :D

thomas:

--- Quote from: dk on April 17, 2009, 09:00:01 am ---I've got a crash of Code::Blocks last nightly , when moving toolbars or other windows.
--- End quote ---
Yes, I've seen this happen under Ubuntu (using the official build bundled with Jaunty Jackalope) too, but only when running Code::Blocks on a remote X server. On top of that, Code::Blocks is practically unusable in that environment, as it takes between half a second and two seconds before a mouse click is realized (1000 MBit network with about 3 meters total cable length). It takes about 20 seconds just to start up, as well.
The same copy of Code::Blocks started locally on the same machine fires up in little over a second, runs perfectly reliably, and exposes the same perceived speed as the Windows build. All other applications that I'm using work seemingly the same whether run locally or via network (no noticeable difference at all).

Not sure what it is, but I guess wxGTK is having an issue there, somehow the event loop not coping well with network, or whatever...?

mmkider:

--- Quote from: thomas on April 17, 2009, 11:45:08 am ---
--- Quote from: dk on April 17, 2009, 09:00:01 am ---I've got a crash of Code::Blocks last nightly , when moving toolbars or other windows.
--- End quote ---
Yes, I've seen this happen under Ubuntu (using the official build bundled with Jaunty Jackalope) too, but only when running Code::Blocks on a remote X server. On top of that, Code::Blocks is practically unusable in that environment, as it takes between half a second and two seconds before a mouse click is realized (1000 MBit network with about 3 meters total cable length). It takes about 20 seconds just to start up, as well.
The same copy of Code::Blocks started locally on the same machine fires up in little over a second, runs perfectly reliably, and exposes the same perceived speed as the Windows build. All other applications that I'm using work seemingly the same whether run locally or via network (no noticeable difference at all).

Not sure what it is, but I guess wxGTK is having an issue there, somehow the event loop not coping well with network, or whatever...?

--- End quote ---
See my post(Sorry, I lost the  password of mmkider :( ), and add one line code.
I always  "never" get crash when I drag the toolbar. :lol:
 
http://wxforum.shadonet.com/viewtopic.php?t=23624&highlight=bug+wxmsw

pasgui:

--- Quote from: wagb278 on April 17, 2009, 03:58:38 am ---I am running on Ubuntu 64-bit.  It is not a file permission access problem (they are under my home directory).

--- End quote ---

Which version of Ubuntu ?

Best regards, pasgui

Xaviou:

--- Quote from: wagb278 on April 17, 2009, 03:58:38 am ---Since updating to SVN 5534 none of my projects will open on Code::Blocks.  Was there a change that requires me to do something to the project files?

I get the SVN updates via Ubuntu package manager updates as third party updates which has always worked before. I notice the build number is one less than this message thread title. Does that have something to do with my issue?

The About dialog says I am running: svn build rev 5534 (2009-04-13 14:47:54) gcc 3.1.2 Linux/unicode

I get a dialog saying - "Can't open file. Do you want to remove if from the recent file list?"

I am running on Ubuntu 64-bit.  It is not a file permission access problem (they are under my home directory).

--- End quote ---

I confirm this.
As I am the one who made the deb files, I'll try to make a full rebuild, to see if it works better.

About the rev number : I don't know why, but after a checkout to rev 5535, the build gives a 5534 (it happens on Linux and on Windows). Is it a known behaviour ? Can someone explain this ?

For the moment, I'll tell Ubuntu amd64 users to not do the update, until the package hasn't been rebuild.

Sorry for the inconvenience.

Regards
Xav'

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version