News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Codeblocks crash on linux when building single file

Started by Ghorgoth, January 10, 2014, 11:30:33 AM

Previous topic - Next topic

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Ghorgoth

Quote from: jens on January 21, 2014, 06:34:35 AM
Quote from: Ghorgoth on January 20, 2014, 02:51:12 PM
Thanks for solving this issue!
I can't compile right now for linux but i'll check as soon as i can or a nightly gets released.
For CentOS, Fedora and Ddebian you can find nightlies of actual trunk on my server.
See my signature for urls.

I just tried on Centos6 and it works, thanks everyone!

oBFusCATed

@killerbot:
The regression should be fixed in trunk.
I prefer C::B to not clear the "Build log" as long as possible, so I can see as much history as possible.
If you think this is not OK for this case please say so and I'll revert the change.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

killerbot

confirmed that the regression is fixed.

Question : what is now the extected behavior when the build log gets cleared.

Test result :
- clean library ==> cleans
- build library ==> builds and the output of the previous clean removed
- build library again ==> outputs nothing to be done, and previous build log removed

[in that library touch 1 file]

Compile that single file :
- builds file ==> new log, AND previous log not removed
- build that file again  ===> new log, and previous logS not removed
- build that file again  ===> new log (nothing to be done), and previous logS not removed ...... and so on

Is a little bit inconsistent, so just wondering what is the new behavior/algorithm ?

nenin

I have similar issue on Win7 64b. Build of the single file from big project sometimes forces C::B to hung. But I can not reproduce it. This issue appeared 3 or 4 times.

oBFusCATed

Switch to the svn trunk build or wait for the next night build.
If the problem shows up again please report.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]