[test] linking does not return
Hello, I've some test files but the link-step does not return (waits forever). gcc.link ../../../bin.v2/libs/tp/test/test_bounded_queue_fifo.test/gcc-4.3.1/debug/link-static/threading-multi/test_bounded_queue_fifo The Jam file: import testing ; project : requirements <library>../../test/build//boost_unit_test_framework <library>../../thread/build//boost_thread <library>../../system/build//boost_system <link>static <threading>multi ; rule tp-test ( source ) { return [ run $(source).cpp ] ; } test-suite thread_pool : [ tp-test test_bounded_queue_fifo ] [ tp-test test_bounded_queue_lifo ] [ tp-test test_bounded_queue_priority ] [ tp-test test_bounded_queue_smart ] [ tp-test test_unbounded_queue_fifo ] [ tp-test test_unbounded_queue_lifo ] [ tp-test test_unbounded_queue_priority ] [ tp-test test_unbounded_queue_smart ] ; Platform LINUX (Debian/Lenny). regards, Oliver
k-oli@gmx.de wrote:
Hello, I've some test files but the link-step does not return (waits forever).
gcc.link ../../../bin.v2/libs/tp/test/test_bounded_queue_fifo.test/gcc-4.3.1/debug/link-static/threading-multi/test_bounded_queue_fifo
If the linker fails to complete, it is a bug in the linker. You probably can report that to the binutils folks. If you're on debian, you should report it to debian folks, using reportbug tool, or however it's called these days. Of course, a minimal test case will be desired. If you can attach to linker with gdb and figure where it's stuck, it might help too. If you're building on a network disk, you might want to try on local -- I used to get hangs like this when a file was open in Windows via samba. - Volodya
I check it on Win-XP - the linker also hangs. My code is missing something - but I don't know. I've appended Jam and test file. I hope you can give me some hints. regards, Oliver Am Montag, 27. Oktober 2008 20:52:30 schrieb Vladimir Prus:
k-oli@gmx.de wrote:
Hello, I've some test files but the link-step does not return (waits forever).
gcc.link ../../../bin.v2/libs/tp/test/test_bounded_queue_fifo.test/gcc-4.3.1/debug /link-static/threading-multi/test_bounded_queue_fifo
If the linker fails to complete, it is a bug in the linker. You probably can report that to the binutils folks. If you're on debian, you should report it to debian folks, using reportbug tool, or however it's called these days. Of course, a minimal test case will be desired. If you can attach to linker with gdb and figure where it's stuck, it might help too.
If you're building on a network disk, you might want to try on local -- I used to get hangs like this when a file was open in Windows via samba.
- Volodya
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
I've sent this before so apologies if it arrives twice (somehow gmail is going crazy on me) This can occur if you enter an infinite loop inside one of your tests, then it will look like it hangs on the link step because that is the last message that will appear on the terminal. BJam should flush its output, or is Boost.Test at fault here too? Output should look like this: gcc.link ../../../...gcc-4.3.2/debug/link-static/shift testing.unit-test ../../../...gcc-4.3.2/debug/link-static/shift.passed Running 12 test cases...
participants (3)
-
k-oli＠gmx.de -
Kevin Sopp -
Vladimir Prus