From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA 4/4 take 2] Improved linker-debugger interface
Date: Wed, 15 Aug 2012 17:24:00 -0000 [thread overview]
Message-ID: <20120815172346.GA5696@host2.jankratochvil.net> (raw)
In-Reply-To: <20120719110518.GE16185@redhat.com>
Hi Gary,
(1)
with the current setup IIRC the dlmopen()ed libraries are only shown with live
process but they cannot be shown when loaded from a core file.
This breaks functionality of core files, I believe glibc needs an extension if
it currently cannot be done otherwise.
(2)
solib-svr4.c is current not used by with gdbsrver and its recent
linux_qxfer_libraries_svr4.
Your testcases is skipped if [is_remote target], with the current general goal
to unify linux-nat with gdbserver and drop linux-nat afterwards I do not think
we should accept more patches increasing the linux-nat vs. gdbserver gap.
The testcase should be specifically compatible with gdbserver.
To give the background: solib-svr4.c is more general and it is kept for all
possible corner cases, it also supports more OSes than just GNU/Linux.
Compared to it linux-low.c can be easier, this is why it is reimplemented and
not shared with solib-svr4.c (it could be shared more but it is not).
Therefore maybe your extensions on top of it all are not feasible for
gdb/common/ but they should be at least reimplemented also for linux-low.c
(3)
There is some issue we already discussed off-list, in some cases (Fedora
Rawhide x86_64 with Fedora patched GDB) it breaks on
FAIL: gdb.base/break-dlmopen.exp: info sharedlibrary #5
namespace_update_full(lmid=0x1,debug_base=0x7ffff7ffd0f8,is_initial_ns=0
svr4_read_so_list(lm=0x6020a0,prev_lm=0x0)
lm=0x6020a0={next=0x602670,prev=0x0}
lm=0x602670={next=0x0,prev=0x0}
warning: Corrupted shared library list: 0x6020a0 != 0x0
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.
Thanks,
Jan
next prev parent reply other threads:[~2012-08-15 17:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 11:09 Gary Benson
2012-07-25 19:36 ` Tom Tromey
2012-07-31 12:12 ` Gary Benson
2012-07-31 12:13 ` Gary Benson
2012-08-14 19:49 ` Tom Tromey
2012-08-15 17:24 ` Jan Kratochvil [this message]
2012-08-15 17:46 ` Jan Kratochvil
2012-08-16 11:14 ` Gary Benson
2012-08-16 15:52 ` Gary Benson
2012-08-17 10:54 ` Gary Benson
2012-08-17 16:41 ` Jan Kratochvil
2012-09-19 9:49 ` Gary Benson
2012-09-19 11:14 ` Jan Kratochvil
2012-09-19 15:06 ` Gary Benson
2012-09-19 15:13 ` Jan Kratochvil
2012-09-21 12:36 ` Gary Benson
2012-09-21 14:46 ` Jan Kratochvil
2012-09-28 10:51 ` Gary Benson
2012-09-28 10:58 ` Jan Kratochvil
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=20120815172346.GA5696@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@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