From: Ben Cheng <bccheng@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Ignore the first entry returned by svr4_current_sos_via_xfer_libraries for dynamically linked programs
Date: Tue, 04 Jun 2013 18:18:00 -0000 [thread overview]
Message-ID: <CAPk6zkAcnGG4Jg=S_N_zBXefsaW0QjMc-m3B7Z-riQgZfkL24Q@mail.gmail.com> (raw)
In-Reply-To: <20130604180722.GA23588@host2.jankratochvil.net>
Hmm this problem only shows up after I refresh gdbserver from the
unmodified gdb 7.6 tree. As you mentioned, gdb 7.1 did not support
library-list-svr4, so when I paired gdbserver 7.1 with gdb 7.6 they
also work fine.
On Tue, Jun 4, 2013 at 11:07 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> Hi Ben,
>
> On Tue, 28 May 2013 20:31:31 +0200, Ben Cheng wrote:
>> The first entry in the xml list returned by
>> svr4_current_sos_via_xfer_libraries() is the executable itself.
> [...]
> http://sourceware.org/bugzilla/show_bug.cgi?id=15507
>> Currently Android is using gdbserver from 7.1 and gdb from 7.3.
> [...]
>> <library-list-svr4 version="1.0"><library name="<test_program>"
>> lm="0xb6fed108" l_addr="0x0" l_ld="0x0"/><library name="/system/bin/linker"
>
> in fact this GDB patch should be dropped.
>
> Bug is in the Android gdbsever implementation. FSF gdbserver 7.1 did not
> support <library-list-svr4/> at all, this feature is in gdbserver 7.4+ only.
>
> Main executable should not have an entry, it has only "main-lm" attribute:
> info '(gdb)Library List Format for SVR4 Targets'
> Additionally the single `main-lm' attribute specifies address of
> `struct link_map' used for the main executable.
>
> GNU/Linux FSF gdbserver-HEAD list looks like:
>
> Sending packet: $qXfer:libraries-svr4:read::0,fff#91...Packet received: l<library-list-svr4 version="1.0" main-lm="0x7ffff7ffe208"><library name="/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/gcore-relro-lib.so" lm="0x7ffff7ff97f0" l_addr="0x7ffff7bda000" l_ld="0x7ffff7ddadf8"/><library name="/lib64/libm.so.6" lm="0x7ffff7fe8000" l_addr="0x7ffff78d8000" l_ld="0x7ffff7bd8da8"/><library name="/lib64/libc.so.6" lm="0x7ffff7fe84c8" l_addr="0x7ffff7518000" l_ld="0x7ffff78d0b80"/><library name="/lib64/ld-linux-x86-64.so.2" lm="0x7ffff7ffd998" l_addr="0x7ffff7ddc000" l_ld="0x7ffff7ffcdf0"/></library-list-svr4>^M
>
>
> Regards,
> Jan
next prev parent reply other threads:[~2013-06-04 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 18:31 Ben Cheng
2013-05-29 10:17 ` Gary Benson
2013-06-04 8:58 ` Jan Kratochvil
2013-06-04 17:19 ` Ben Cheng
2013-06-04 18:07 ` Jan Kratochvil
2013-06-04 18:18 ` Ben Cheng [this message]
2013-06-04 20:23 ` Jan Kratochvil
2013-06-04 20:36 ` Ben Cheng
2013-06-04 20:45 ` Ben Cheng
2013-06-04 20:57 ` Jan Kratochvil
2013-06-04 21:21 ` Ben Cheng
2013-06-05 11:38 ` [patchv2] " Jan Kratochvil
[not found] ` <51AF4C5B.5080104@redhat.com>
2013-06-09 18:08 ` [commit] " Jan Kratochvil
2013-06-11 6:32 ` Ben Cheng
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='CAPk6zkAcnGG4Jg=S_N_zBXefsaW0QjMc-m3B7Z-riQgZfkL24Q@mail.gmail.com' \
--to=bccheng@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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