gdbserver远程调试ctrl＋c

ruger

用gdbserver远程调试ctrl+c出现的segment fault
但是在PC上运行ppc_85xx-gdb，设置target remote，c，出现：

1. 
   
2. Remote debugging using 192.168.2.206:2345
   
3. 0x30010564 in ?? ()
   
4. (gdb) c
   
5. Continuing.
   
6. 
   
7. Program received signal SIG32, Real-time event 32.
   
8. 0x0fef2aa0 in ?? ()
   
9. (gdb) c
   
10. Continuing.
    
11. 
    
12. Program received signal SIG32, Real-time event 32.
    
13. 0x0fef2aa0 in ?? ()
    
14. (gdb) c
    
15. Continuing.
    
16. c
    
17. c
    
18. c
    
19. 
    
20. Program received signal SIGINT, Interrupt.
    
21. 0x0fef6714 in ?? ()
    
22. (gdb) c
    
23. Continuing.
    
24. 
    

复制代码

？？太多了，我想知道段错误的具体位置，请问怎么调试，谢谢

[ 本帖最后由 ruger 于 2008-12-10 13:15 编辑 ]

T-bagwell

确实挺痛苦的,期待高手的答案

[ 本帖最后由 T-bagwell 于 2008-12-10 12:02 编辑 ]

emmoblin

我以前调试的时候一个好方法是
首先得busybox得是高点的版本，好像得1.0以上吧，
反正得支持ulimit。
然后开打ulimit记录，具体怎么弄你慢一下。
反正让他段错误的时候产生core文件。
然后你把这个core文件传到pc机，用ppc_gdb -c ./core  filename
加载后，用bt查看一下堆栈就知道断在哪了

ruger

原帖由 emmoblin 于 2008-12-10 12:52 发表
我以前调试的时候一个好方法是
首先得busybox得是高点的版本，好像得1.0以上吧，
反正得支持ulimit。
然后开打ulimit记录，具体怎么弄你慢一下。
反正让他段错误的时候产生core文件。
然后你把这个core文件 ...

试试～～
ulimit支持，ulimit -c 10244
./server后ctrl+c
产生了core文件，core.524
但是ppc_85xx-gdb --core=core.524还是看不到具体错误的位置：

1. 
   
2. [root@localhost order]# ppc_85xx-gdb --core=core.524
   
3. GNU gdb Red Hat Linux (6.3.0.0-1.21_1rh)
   
4. Copyright 2004 Free Software Foundation, Inc.
   
5. GDB is free software, covered by the GNU General Public License, and you are
   
6. welcome to change it and/or distribute copies of it under certain conditions.
   
7. Type "show copying" to see the conditions.
   
8. There is absolutely no warranty for GDB.  Type "show warranty" for details.
   
9. This GDB was configured as "--host=i386-redhat-linux --target=ppc-linux".
   
10. Core was generated by `./server'.
    
11. Program terminated with signal 11, Segmentation fault.
    
12. #0  0x0fdf5644 in ?? ()
    
13. (gdb) bt
    
14. #0  0x0fdf5644 in ?? ()
    
15. #1  0x0fed4b3c in ?? ()
    
16. Previous frame identical to this frame (corrupt stack?)
    
17. (gdb) file ./server
    
18. Reading symbols from /root/workspace/code/order/server...done.
    
19. (gdb) bt
    
20. #0  0x0fdf5644 in ?? ()
    
21. #1  0x0fed4b3c in ?? ()
    
22. Previous frame identical to this frame (corrupt stack?)
    

复制代码

我的libthread_db.so是stripped的，是否stripped后的libthread_db不支持具体的错误信息？

[ 本帖最后由 ruger 于 2008-12-10 13:38 编辑 ]

T-bagwell

得给分,提供的思路很好

emmoblin

试试吧，以前我就是这么干的

ruger

ulimit支持，ulimit -c 10244
./server后ctrl+c
产生了core文件，core.524
但是ppc_85xx-gdb --core=core.524还是看不到具体错误的位置：

1. 
   
2. [root@localhost order]# ppc_85xx-gdb --core=core.524
   
3. GNU gdb Red Hat Linux (6.3.0.0-1.21_1rh)
   
4. Copyright 2004 Free Software Foundation, Inc.
   
5. GDB is free software, covered by the GNU General Public License, and you are
   
6. welcome to change it and/or distribute copies of it under certain conditions.
   
7. Type "show copying" to see the conditions.
   
8. There is absolutely no warranty for GDB.  Type "show warranty" for details.
   
9. This GDB was configured as "--host=i386-redhat-linux --target=ppc-linux".
   
10. Core was generated by `./server'.
    
11. Program terminated with signal 11, Segmentation fault.
    
12. #0  0x0fdf5644 in ?? ()
    
13. (gdb) bt
    
14. #0  0x0fdf5644 in ?? ()
    
15. #1  0x0fed4b3c in ?? ()
    
16. Previous frame identical to this frame (corrupt stack?)
    
17. (gdb) file ./server
    
18. Reading symbols from /root/workspace/code/order/server...done.
    
19. (gdb) bt
    
20. #0  0x0fdf5644 in ?? ()
    
21. #1  0x0fed4b3c in ?? ()
    
22. Previous frame identical to this frame (corrupt stack?)
    

复制代码

我的libthread_db.so是stripped的，是否stripped后的libthread_db不支持具体的错误信息？

ruger

我查源代码找到一个明显的错误。。。,寒～～