2013-05-26 66 views
3

全部使用GDB调试多线程程序(openmp)

我打算在Fedora中使用gdb调试24个线程的程序,并且我有以下GDB输出。当我想切换到发生分段错误的特定线程时,我无法使用线程命令(GDB输出中的最后4行)切换到该线程。你能帮我一下吗?你知道它是什么错误吗? GDB输出如下:

[[email protected] nameComponentEncoding]# gdb NCE_david 
GNU gdb (GDB) Fedora (7.2.90.20110429-36.fc15) 
Copyright (C) 2011 Free Software Foundation, Inc. 
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> 
This is free software: you are free to change and redistribute it. 
There is NO WARRANTY, to the extent permitted by law. Type "show copying" 
and "show warranty" for details. 
This GDB was configured as "x86_64-redhat-linux-gnu". 
For bug reporting instructions, please see: 
<http://www.gnu.org/software/gdb/bugs/>... 
Reading symbols from /mnt/disk2/experiments_BLOODMOON/two_stage_bloom_filter/programs/nameComponentEncoding/NCE_david 
(gdb) r 
Starting program: 
[Thread debugging using libthread_db enabled] 

[New Thread 0x7fffd2bf5700 (LWP 11538)] 
[New Thread 0x7fffd23f4700 (LWP 11539)] 
[New Thread 0x7fffd1bf3700 (LWP 11540)] 
[New Thread 0x7fffd13f2700 (LWP 11541)] 
[New Thread 0x7fffd0bf1700 (LWP 11542)] 
[New Thread 0x7fffd03f0700 (LWP 11543)] 
[New Thread 0x7fffcfbef700 (LWP 11544)] 
[New Thread 0x7fffcf3ee700 (LWP 11545)] 
[New Thread 0x7fffcebed700 (LWP 11546)] 
[New Thread 0x7fffce3ec700 (LWP 11547)] 
[New Thread 0x7fffcdbeb700 (LWP 11548)] 
[New Thread 0x7fffcd3ea700 (LWP 11549)] 
[New Thread 0x7fffccbe9700 (LWP 11550)] 
[New Thread 0x7fffcc3e8700 (LWP 11551)] 
[New Thread 0x7fffcbbe7700 (LWP 11552)] 
[New Thread 0x7fffcb3e6700 (LWP 11553)] 
[New Thread 0x7fffcabe5700 (LWP 11554)] 
[New Thread 0x7fffca3e4700 (LWP 11555)] 
[New Thread 0x7fffc9be3700 (LWP 11556)] 
[New Thread 0x7fffc93e2700 (LWP 11557)] 
[New Thread 0x7fffc8be1700 (LWP 11558)] 
[New Thread 0x7fffc83e0700 (LWP 11559)] 
[New Thread 0x7fffc7bdf700 (LWP 11560)] 

Program received signal SIGSEGV, Segmentation fault. 
[Switching to Thread 0x7fffd2bf5700 (LWP 11538)] 
compare (__str="art", this=0xbf934d0) at /usr/lib/gcc/x86_64-redhat-linux/4.6.0/ 
2175   const size_type __size = this->size(); 
(gdb) thread 11538 
Thread ID 11538 not known. 
(gdb) thread 0x7fffd2bf5700 
Thread ID -759212288 not known. 

回答

5

GDB有自己的线程编号。这样做:

(gdb) info threads 

    Id Target Id   Frame 
    <... snip ...> 
    2 Thread 0x7ffff7fc1700 (LWP 11538) ... 
* 1 Thread 0x7ffff7fc2740 (LWP 11537) ... 
# thread with PID 11538 is GDB thread number 2 
(gdb) thread 2 

Program received signal SIGSEGV, Segmentation fault. 
[Switching to Thread 0x7fffd2bf5700 (LWP 11538)] 
compare (__str="art", this=0xbf934d0) at /usr/lib/gcc/x86_64-redhat-linux/4.6.0/ 
2175   const size_type __size = this->size(); 

它似乎是段错误是由线程11538.造成使用pthread_setname_np()来命名你的线程会使调试在GDB容易。

我的猜测是,this,C++实例变量,在那一点上是空的(很容易验证),你的情况是一个“免费使用后”的错误。

+0

是的,它的工作原理。你认为分段错误发生在该线程11538上吗? – Bloodmoon

+0

@血月,是的。我已经修改了我的答案。 – scottt

+0

非常感谢。我是GDB的新手,在切换到线程后,我不知道下一步该怎么做。我不知道应该在哪里添加断点......我是否应该推断'compare()'函数的调用位置,并在那里添加断点? – Bloodmoon