id linux.so.2,在Linux中GDB核心转储：通过build-id查找可执行文件

有可能让gdb自动找到相应的可执行文件吗？我已经解压缩了调试符号并将它们放在/usr/lib/debug/.build-id/目录中.当我用gdb /usr/bin/executable core启动gdb时,一切正常.可执行文件和所有共享库的所有调试符号都会自动加载,因为gdb知道build-id并自动加载它.

$gdb /usr/bin/executable core

GNU gdb (GDB) 7.0.1-debian

Copyright (C) 2009 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later

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 "i486-Linux-gnu".

For bug reporting instructions, please see:

...

Reading symbols from /usr/bin/executable...Reading symbols from /usr/lib/debug/.build-id/b7/fada8ba917de74a6055647f3ac205dee1615c8.debug...done.

但是,当我刚启动gdb并加载核心文件时,不会加载任何调试符号.

(gdb) core-file core

[New Thread 10822]

[New Thread 10812]

Core was generated by `/usr/bin/executable'.

Program terminated with signal 6, Aborted.

#0 0xb7790424 in __kernel_vsyscall ()

使用strace运行gdb表明它甚至没有尝试找到它们.核心文件包含build-id,所以我猜gdb应该能够找到它…

$eu-unstrip -n --core core

0x8048000+0x25d000 [email protected] - - [exe]

0xb7790000+0x1000 [email protected] . - Linux-gate.so.1

0xb7771000+0x19000 [email protected] /lib/i686/cmov/libpthread.so.0 - libpthread.so.0

0xb7768000+0x9000 [email protected] /lib/i686/cmov/librt.so.1 - librt.so.1

0xb7672000+0xf5000 [email protected] /usr/lib/libstdc++.so.6 - libstdc++.so.6

0xb764c000+0x26000 [email protected] /lib/i686/cmov/libm.so.6 - libm.so.6

0xb762e000+0x1e000 [email protected] /lib/libgcc_s.so.1 - libgcc_s.so.1

0xb74e7000+0x147000 [email protected] /lib/i686/cmov/libc.so.6 - libc.so.6

0xb7791000+0x1d000 [email protected] /lib/ld-Linux.so.2 - ld-Linux.so.2

有没有办法让gdb查找可执行文件的调试文件而不提供导致核心转储的可执行文件？

您可以尝试直接加载调试符号：

(gdb) symbol-file /tmp/your_debug_symbols.dbg

但我不认为coredump本身对GDB来说已经足够了,需要提供可执行文件才能理解核心转储.