std :: thread使用gcc-linaro-4.9.4在Raspbian中导致分段错误

时间:2019-03-14 07:44:07

标签: c++ g++ raspbian stdthread

我在对我看来完全有效的代码上遇到了分段错误。

这是一个最小的重新创建示例:

#include <iostream>
#include <thread>

void func()
{
    /* do nothing; thread contents are irrelevant */
}

int main()
{
    for (unsigned idx = 0; idx < 1000; idx++)
    {
        std::thread t(func);
        void* buffer = malloc(1000);
        free(buffer);
        t.join();
    }
    return 0;
} 

我进行了打印,以检查哪个迭代失败;我在第292次迭代中遇到了细分错误。

我使用了gcc-linaro-4.9.4(摘自https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/arm-linux-gnueabihf/)。

我以这种方式编译程序:

arm-linux-gnueabihf-g++ -std=c++11 -std=gnu++11 -lpthread -pthread main.cpp -o main.out

我尝试在gcc-linaro-6.5中重新创建它,但那里没有问题。

知道为什么会这样吗?

编辑1

编译此代码时没有警告/错误。

在strace下运行它并没有什么特别的。

在GDB下运行它表明分段错误发生在free函数中:

Thread 1 "main.out" received signal SIGSEGV, Segmentation fault.
_int_free (av=0x76d84794 <main_arena>, p=0x1e8bf, have_lock=0) at malloc.c:4043
4043    malloc.c: No such file or directory.
(gdb) bt
#0  _int_free (av=0x76d84794 <main_arena>, p=0x1e8bf, have_lock=0) at malloc.c:4043
#1  0x00010bfa in main ()

在valgrind下运行它会显示以下内容:

==361== Thread 2:
==361== Invalid read of size 4
==361==    at 0x4951D64: ??? (in /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==361==  Address 0x4becf74 is 0 bytes after a block of size 28 alloc'd
==361==    at 0x4847D4C: operator new(unsigned int) (vg_replace_malloc.c:328)
==361==    by 0x11629: __gnu_cxx::new_allocator<std::_Sp_counted_ptr_inplace<std::thread::_Impl<std::_Bind_simple<void (*())()> >, std::allocator<std::thread::_Impl<std::_Bind_simple<void (*())()> > >, (__gnu_cxx::_Lock_policy)2> >::allocate(unsigned int, void const*) (in /home/pi/main.out)
==361== 
==361== Invalid write of size 4
==361==    at 0x4951D6C: ??? (in /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==361==  Address 0x4becf74 is 0 bytes after a block of size 28 alloc'd
==361==    at 0x4847D4C: operator new(unsigned int) (vg_replace_malloc.c:328)
==361==    by 0x11629: __gnu_cxx::new_allocator<std::_Sp_counted_ptr_inplace<std::thread::_Impl<std::_Bind_simple<void (*())()> >, std::allocator<std::thread::_Impl<std::_Bind_simple<void (*())()> > >, (__gnu_cxx::_Lock_policy)2> >::allocate(unsigned int, void const*) (in /home/pi/main.out)
==361== 
==361== 
==361== HEAP SUMMARY:
==361==     in use at exit: 28,000 bytes in 1,000 blocks
==361==   total heap usage: 2,002 allocs, 1,002 frees, 1,048,368 bytes allocated
==361== 
==361== Thread 1:
==361== 28,000 bytes in 1,000 blocks are definitely lost in loss record 1 of 1
==361==    at 0x4847D4C: operator new(unsigned int) (vg_replace_malloc.c:328)
==361==    by 0x11629: __gnu_cxx::new_allocator<std::_Sp_counted_ptr_inplace<std::thread::_Impl<std::_Bind_simple<void (*())()> >, std::allocator<std::thread::_Impl<std::_Bind_simple<void (*())()> > >, (__gnu_cxx::_Lock_policy)2> >::allocate(unsigned int, void const*) (in /home/pi/main.out)
==361== 
==361== LEAK SUMMARY:
==361==    definitely lost: 28,000 bytes in 1,000 blocks
==361==    indirectly lost: 0 bytes in 0 blocks
==361==      possibly lost: 0 bytes in 0 blocks
==361==    still reachable: 0 bytes in 0 blocks
==361==         suppressed: 0 bytes in 0 blocks
==361== 
==361== For counts of detected and suppressed errors, rerun with: -v
==361== ERROR SUMMARY: 2017 errors from 3 contexts (suppressed: 6 from 3)

编辑2

删除-lpthread-std=c++11编译标志后,仍然出现隔离错误。这是我这次的编译方式:

arm-linux-gnueabihf-g++ -std=gnu++11 -pthread main.cpp -o main.out

1 个答案:

答案 0 :(得分:0)

我认为问题是您的代码与您链接到的libstdc++.so库之间不匹配。

一种可能性是在运行时使用了错误的libstdc++.so,您可以使用ldd实用程序进行检查。 GCC 4.9.4的正确版本是libstdc++.so.6.0.20,因此,如果您看到它链接到其他版本,那就是问题。

第二种可能性是它是正确的libstdc++.so,但是它的编译设置与您的代码不同,因此代码中的std::thread使用原子操作进行shared_ptr引用计数,但是库中的std::thread使用了互斥锁(与GCC Bug 42734中描述的问题相同)。如果使用-march=armv5t编译程序时崩溃和valgrind错误消失了,那么可以确认这是问题所在。