Now that we've switched everyone back to testing the trunk I though I'd bring this test up. When one is lucky, it fails with a "memory access violation" in *all* platforms. When one isn't lucky, which seems to be just about all the time on my Linux machine, one gets an interrupt from libc with an accompanying stack dump: *** glibc detected *** /home/grafik/devroots/Boost/boost-trunk-testing/results/boost/bin.v2/libs/graph/test/csr_graph_test.test/gcc-4.2.0~linux~x86/debug/csr_graph_test: free(): invalid size: 0x08091818 *** ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6[0xb7cdf7cd] /lib/tls/i686/cmov/libc.so.6[0xb7ce04da] /lib/tls/i686/cmov/libc.so.6(__libc_malloc+0x7e)[0xb7ce160e] /usr/local/gcc-4.2.0/lib/libstdc++.so.6(__cxa_allocate_exception+0x22)[0xb7eac3a2] /home/grafik/devroots/Boost/boost-trunk-testing/results/boost/bin.v2/libs/graph/test/csr_graph_test.test/gcc-4.2.0~linux~x86/debug/csr_graph_test[0x804c797] /home/grafik/devroots/Boost/boost-trunk-testing/results/boost/bin.v2/libs/graph/test/csr_graph_test.test/gcc-4.2.0~linux~x86/debug/csr_graph_test[0x804c86f] /home/grafik/devroots/Boost/boost-trunk-testing/results/boost/bin.v2/libs/graph/test/csr_graph_test.test/gcc-4.2.0~linux~x86/debug/csr_graph_test[0x804d680] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb7c8debc] /home/grafik/devroots/Boost/boost-trunk-testing/results/boost/bin.v2/libs/graph/test/csr_graph_test.test/gcc-4.2.0~linux~x86/debug/csr_graph_test(_ZNSt15basic_streambufIcSt11char_traitsIcEE6xsputnEPKci+0x41)[0x804af91] ======= Memory map: ======== 08048000-0807c000 r-xp 00000000 03:01 879620 /home/grafik/devroots/Boost/boost-trunk-testing/results/boost/bin.v2/libs/graph/test/csr_graph_test.test/gcc-4.2.0~linux~x86/debug/csr_graph_test 0807c000-0807d000 rw-p 00034000 03:01 879620 /home/grafik/devroots/Boost/boost-trunk-testing/results/boost/bin.v2/libs/graph/test/csr_graph_test.test/gcc-4.2.0~linux~x86/debug/csr_graph_test 0807d000-080c0000 rw-p 0807d000 00:00 0 [heap] [...] ************************* ~~~~ ************************* Which wouldn't be so bad, except that it halts the testing. And hence prevents posting any results. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera wrote:
Which wouldn't be so bad, except that it halts the testing. And hence prevents posting any results.
PS. I should have mentioned... That after some point if this test continues to behave badly I'll have to disable it so we can progress with testing. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
On Aug 16, 2007, at 12:27 PM, Rene Rivera wrote:
Now that we've switched everyone back to testing the trunk I though I'd bring this test up. When one is lucky, it fails with a "memory access violation" in *all* platforms. When one isn't lucky, which seems to be just about all the time on my Linux machine, one gets an interrupt from libc with an accompanying stack dump:
Sorry, I'll try to get this fixed today. - Doug
On Aug 16, 2007, at 1:43 PM, Doug Gregor wrote:
On Aug 16, 2007, at 12:27 PM, Rene Rivera wrote:
Now that we've switched everyone back to testing the trunk I though I'd bring this test up. When one is lucky, it fails with a "memory access violation" in *all* platforms. When one isn't lucky, which seems to be just about all the time on my Linux machine, one gets an interrupt from libc with an accompanying stack dump:
Sorry, I'll try to get this fixed today.
Ugh. Well, *now* it's fixed. - Doug
participants (2)
-
Doug Gregor -
Rene Rivera