From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ansis Atteka <ansisatteka.dev@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Why GDB ignores relative RPATH to find shared libraries?
Date: Sun, 21 Nov 2010 18:26:00 -0000 [thread overview]
Message-ID: <20101121182635.GA24208@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTi=q4hnvgg_J514Q-Z1F1Pg6HNUuLGKRyYor2NmB@mail.gmail.com>
On Fri, 19 Nov 2010 02:31:11 +0100, Ansis Atteka wrote:
> It seems that GDB favours the paths to shared libraries specified in
> coredump file instead of those specified in executable
It does not favor them but it never reads them at all. GDB uses only the
_r_debug inferior shared library list.
rm -rf xbin xlib core.*;mkdir xbin xlib;:|gcc -x c - -shared -fPIC -o xlib/libx.so -Wl,-soname,libx.so;echo 'main(){*(int*)0=0;}'|gcc -o xbin/bin -x c - -Lxlib -lx -Wl,-rpath,'$ORIGIN/../xlib';(ulimit -c unlimited;./xbin/bin);gdb -nx xbin/bin ./core.*
define sharedlist
set var $sharedlist_iter=_r_debug.r_map
while ($sharedlist_iter)
print $sharedlist_iter->l_name
set var $sharedlist_iter=$sharedlist_iter->l_next
end
end
(gdb) sharedlist
$5 = 0x35f0419a74 ""
$6 = 0x35f0419a74 ""
$7 = 0x7f56709fb7b0 "/home/jkratoch/t/libs/xbin/../xlib/libx.so"
$8 = 0x7f56709fbca0 "/lib64/libc.so.6"
$9 = 0x400200 "/lib64/ld-linux-x86-64.so.2"
There is no $ORIGIN present anywhere in the inferior's list of currently
loaded shared libraries. (Not even in the glibc internal link_map structure.)
This is sometimes a problem you cannot put breakpoints (without just making
them `pending') into shared libraries before you `start' the program, as GDB
does not know which shared libraries may get loaded.
Filed http://sourceware.org/bugzilla/show_bug.cgi?id=12249 RFE for it.
> and that is not portable for remote analysis.
Currently even ld.so never suggests when it used $ORIGIN:
LD_DEBUG=all ./xbin/bin 2>&1 |grep libx|grep -v symbol=
26462: file=libx.so [0]; needed by ./xbin/bin [0]
26462: find library=libx.so [0]; searching
26462: trying file=/home/jkratoch/t/libs/xbin/../xlib/tls/x86_64/libx.so
26462: trying file=/home/jkratoch/t/libs/xbin/../xlib/tls/libx.so
26462: trying file=/home/jkratoch/t/libs/xbin/../xlib/x86_64/libx.so
26462: trying file=/home/jkratoch/t/libs/xbin/../xlib/libx.so
26462: file=libx.so [0]; generating link map
26462: checking for version `GLIBC_2.2.5' in file /lib64/libc.so.6 [0] required by file /home/jkratoch/t/libs/xbin/../xlib/libx.so [0]
26462: relocation processing: /home/jkratoch/t/libs/xbin/../xlib/libx.so (lazy)
26462: binding file /home/jkratoch/t/libs/xbin/../xlib/libx.so [0] to /lib64/libc.so.6 [0]: normal symbol `__cxa_finalize' [GLIBC_2.2.5]
26462: calling init: /home/jkratoch/t/libs/xbin/../xlib/libx.so
But GDB could it from DT_RPATH.
Filed http://sourceware.org/bugzilla/show_bug.cgi?id=12250 RFE for it.
Thanks,
Jan
prev parent reply other threads:[~2010-11-21 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 1:31 Ansis Atteka
2010-11-21 18:26 ` Jan Kratochvil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101121182635.GA24208@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=ansisatteka.dev@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox