Recently, I found that GDB is very useful for us to trace some problem, especially multi-threads related ones. Here are some useful commands for debug those kinds of problems.
1. Ctrl + C: which would pause the gdb debug
2. info local
3. info threads
4. info registers
5. bt
6. p ptr
7. c
8. s
9. b 324
10. b file.cpp:321
11. finish
12. thread 2
13. bt
I used the above commands to debug a Embedded program and fixed a deadlock and coredump problem in it. Those problems are both caused by synchronization between multiple threads. Command 12 (thread numb) is very useful for us to trace system hang related problems, in that it could help us figure out the state of each threads at that moment.
本文介绍了一组使用GDB调试多线程程序的实用命令。通过这些命令,作者成功定位并解决了一个嵌入式程序中的死锁及核心转储问题。特别地,切换线程的命令对于诊断系统挂起的问题非常有效。

被折叠的 条评论
为什么被折叠?



