VERY UNSTABLE linux version but rock solid windows version???

[takeshimiya]

I'm thinking that the crash might be related to a combination of the video driver and something else then (coming from C::B, name it: C::B itself, wxWidgets, wxAUI, ...).

I'm using latest propietary Xorg ATI drivers, and certainly I use intensively other programs using GTK or wxWidgets (like VLC or Firefox), and never experienced any issue of this with another program.

Did I say that this most times happens when doing drag and drop on the panels?
The "strange cursor" that knue reffers about, it's the cursor in a DnD state.

BTW, dragging text also hangs C::B sometimes, altrough this is a Scintilla fault's because it happens in SciTE there too.
Dragging toolbars also hang C::B.

Of course, all of this happens sometimes, not always.

[knue]

Sunshine, lollipops, and rainbows everywhere...

I'd like to them, too

@drivers: I use nvidia driver. And because Takeshi Miya has the same problems with ATI I just don't think this is an driver issue.

@Takeshi Miya: Can you post your _exact_ version of gtk, xorg and wxGTK?

Perhaps this is a very nasty threading problem, which only happens with CPUs of a special speed. And there occurs a deadlock or sth like this.

[Ceniza]

I had that problem too (the one freezing the screen with the drag'n'drop cursor), but right now (revision 2260) I just cannot reproduce it again. I had that problem in an old computer too but haven't tried again (it's a computer in the University I have access to, but haven't used it for about two weeks).

The main change since then (excluding the newest Code::Blocks revision) has been switching to the ATI proprietary driver, and keeping the system up to date everyday.

If it's of any use, the OS is Kubuntu Dapper Flight 4 with the latest version available of everything in the ubuntu repositories, using the ATI proprietary driver also available there.

Kernel: 2.6.15-19-686 with SMP
wxGTK: 2.6.2-1
GTK: 2.8.16 and 1.2.10-18
X.Org: 7.0.0-0

In case the hardware also matters:
Processor: Pentium 4 3.0E (HT enabled)
Video: ATI Radeon 9800 Pro

Don't know if that help you find a pattern.

BTW, the old computer is a Pentium III 800MHz with a nVidia (don't know which one).

[takeshimiya]

Here are:

Distro: Ubuntu 64 Breezy Badger with all the updates applied. No hacking.
Kernel: 2.6.12-9-amd64-generic
GTK: 2.8.6-0ubuntu2
wxGTK: 2.6.1.1.1ubuntu2
Xorg: 6.8.2-77
Xorg-driver-fglrx: 8.20.8-1

CPU: Athlon 64 3000+
Video: ATI Radeon XPRESS 200

[CmKaHo]

At the first: Thanks ~ Settings->Editor problem is not a problem anymore.

After a while I can get problem mentioned by knue. It is really after a wildy clicking, but it is there. My X.Org is 6.9 and i have a standard vesa driver .

The problem is exactly as described by knue.

Except this problem, I have C::B (SVN2260) on 2 different machines Intel P4 3GHz(not SMP kernel)/1GB RAM + AMD Athlon XP /512MB RAM (slack 10.2@current, 2.4.31 kernel, wxGTK 2.6.2 ~ compiled) and running very well.

[Michael]

At the first: Thanks ~ Settings->Editor problem is not a problem anymore.

Did you have codestats plugin activated?

I tested rev2274 on Ubuntu 5.10 with codestats plugin and Settings->Editor crashes C::B.

Best wishes,
Michael

[tiwag]

the crash of CB under linux when using Settings->Environment is coming from

src/environmentsettingsdlg.cpp:180

comment this line out and it works

tested with svn rev 2274 under Ubuntu 5.10

[Der Meister]

As mandrav removed this option in revision 2268 this line has to be removed or it will crash.

But I wonder why I still have this option in the dialog (although it is disabled by the line src/environmentsettingsdlg.cpp:180)...  :shock:

[sethjackson]

As mandrav removed this option in revision 2268 this line has to be removed or it will crash.

But I wonder why I still have this option in the dialog (although it is disabled by the line src/environmentsettingsdlg.cpp:180)...  :shock:

Umm run update.bat or the update script..... I think this should fix it.....  :?

[Der Meister]

Well, I'm using the unix build system. And *actually* after one clean rebuild (and I did more than one since this change) this should be applied (yes, I also made a "make clean-zipfiles")...

[sethjackson]

Well OK. I don't have a *nix right now. On windows though you have to run update.bat or the *.xrc resources won't be updated. I learned this the hard way.

[Michael]

In Linux you should use ./update if you build C::B using CodeBlocks-unix.cbp.

Best wishes,
Michael

[Der Meister]

Yes, that's right. But I don't use Code::Blocks to build Code::Blocks.  :lol: I use plain configure and make. Works really well but I have no idea why this ressource was not updated... Normally make clean-zipfiles && make && make install does the trick... Or at least did it before :/

Edit: Just did a "make clean-zipfiles && make && make install" again and it worked - no idea what went wrong the last time... And now I get the crash, too, of course

[Michael]

I have used make & friends the first time I have built C::B and it worked fine. Anyway, it has taken more than 90 minutes. Using C::B, I can save some minutes and therefore go home earlier .

May be there is an option that should be used to update the ressources or may be a bug. Anyway, I am not an expert with make & friends.

Looking at the update file could also be useful or may be give some hint.

Best wishes,
Michael 

[tiwag]

it is not a make issue, i don't have it in my dialog anymore and i've built using autotools too.