How to debug shared librarys with gdb?

最新推荐文章于 2024-02-25 17:36:10 发布

原创最新推荐文章于 2024-02-25 17:36:10 发布 · 2.7k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#library #signal #application #list #access #kill

Linux/Gnu/Gnome 专栏收录该内容

12 篇文章

订阅专栏

博客介绍了在GDB中为共享库设置断点的方法。一是在main()设置断点，列出共享库源代码或符号名后设置断点，但因库未加载到内存可能无法设置；二是在GDB中设置信号处理程序，如拦截SIGINT信号，程序停止时再设置断点，还可使用kill -l列出系统所有信号。

The simplest method (maybe the only method) is:

1. set a break point in main()

2. list the source code or symbol name of the shared library, and set the break point.

You could use add-symbol-file to load the symbols of the shared library. Use ldd, you can see the link address of this shared library, this is the address for the add-symbol-file command. But even you specify the correct address, because at that time, this library has not been loaded in memory, you can not set a break point. It will prompt such error “Cannot access memory at address 0x00xx00xx”.

Another way, you can set a signal handler in gdb, e.g., (gdb) handle SIGINT stop. Then when you press Ctrl+C, the debugger will intercept the SIGINT signal to debuging application, then it will stop, you can set break point at that time. Use kill -l, you could list all signals in your system.