CC makes cb hang

[killerbot]

with one of the latest changes in CC, CB now always hangs on a project that used to work ok.

I have minimized the project to the below code snippet.

Steps to reproduce :
1) create a console project (C++)
2) open its main.cpp
3) replace the main.cpp content by :

Code Select Expand


#include "boost/filesystem.hpp"


void Copy()
{
boost::filesystem::copy_directory("FooDir", "BarDir");
}

int main()
{
Copy();
return 0;
}

---> all done on linux, make sure you have boost installed somewhere
4) put your cursor just past "boost::filesystem' ===> type '3'   ===> hangs

[oBFusCATed]

Is this with the debugger's branch?
Because the latest two CC commits are not in the branch and they should fix some random threading problems.

[killerbot]

no, just on trunk [I have some machines at home on trunk ;-)  ]

[ollydbg]

Sounds be a big bug, I will check it. I will tell Loaden too.

[Loaden]

Fixed in rev7288.

[killerbot]

I can confirm it is fixed :-)  well done.

[ironhead]

Any chance we can get a new nightly?  It looks like a lot of the CC hangs have been addressed and it would be really nice to be able to take advantage of them. 

[killerbot]

I will kick one out tomorrow.

[ollydbg]

Fixed in rev7288.

great job loaden!!!!! so Fast!!!

[oBFusCATed]

Also another sync to the debugger's branch will be handy, so I can test the fixes, too...
Morten, Jens can you do it?

(Jens, if you tell me the exact commands needed to do the merge, I won't bother you any more:) )

[killerbot]

Also another sync to the debugger's branch will be handy, so I can test the fixes, too...
Morten, Jens can you do it?

(Jens, if you tell me the exact commands needed to do the merge, I won't bother you any more:) )

send those commands to me too please ;-)

[Jenna]

Also another sync to the debugger's branch will be handy, so I can test the fixes, too...
Morten, Jens can you do it?

(Jens, if you tell me the exact commands needed to do the merge, I won't bother you any more:) )

send those commands to me too please ;-)

This is how I do it on commandline in linux:

• cd [path/to/my/debugger-branch/copy]
• make sure it is clean and uptodate
• run: svn merge -r [first revision to be merged]:[last revision to be merged] svn+ssh://jenslody@svn.berlios.de/svnroot/repos/codeblocks/trunk . (note the trailing dot [with a blank before it])
• commit changes with comment "* debugger_branch: merged with trunk (trunk to debugger_branch)"

The first revision to be merged is normally the revision after of (!) the last merge, the last revision to be merged is normally HEAD, the url has to be fixed to fit your needs.
Instead of the url you can use the root-folder of your working-copy of trunk.
Instead of the trailing dot you can use the path to your working copy of the debugger-branch (if you are not inside its root-folder).
To see what will be merged (instead of really doing it), you can use "--dry-run" as for many other svn-commands.

EDIT:
corrected incorrect and dangerous instruction !

[oBFusCATed]

Thanks a lot Jens,
I've added this precious info to the wiki -> http://wiki.codeblocks.org/index.php?title=Version_control

[Jenna]

:oops: I found a serious error in my instructions two posts above :
the first revision to be merged has to be the reviosion of last merge !!

This means all my merges (and the merges done by others with this instruction) are most likely incorrect !!

I will check them all and try to correct them !
Exactly I check all merges done by me, oBFusCATed and killerbot.

[Jenna]

This means all my merges (and the merges done by others with this instruction) are most likely incorrect !!

I will check them all and try to correct them !
Exactly I check all merges done by me, oBFusCATed and killerbot.

Seems like only four files have been involved.

Should be fixed now.

Sorry for the inconvenience.