From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, ppluzhnikov@google.com
Subject: Re: [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2
Date: Tue, 04 Oct 2011 06:11:00 -0000 [thread overview]
Message-ID: <E1RAyE5-0006y9-Bz@fencepost.gnu.org> (raw)
In-Reply-To: <20111003215530.GC20272@host1.jankratochvil.net> (message from Jan Kratochvil on Mon, 3 Oct 2011 23:55:30 +0200)
> Date: Mon, 3 Oct 2011 23:55:30 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Paul Pluzhnikov <ppluzhnikov@google.com>
>
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -36412,15 +36412,21 @@ are loaded.
>
> The @samp{qXfer:libraries:read} packet returns an XML document which
> lists loaded libraries and their offsets. Each library has an
> -associated name and one or more segment or section base addresses,
> -which report where the library was loaded in memory.
> +associated name and one or more segment, section base addresses or SVR4 linker
> +parameters, which report where the library was loaded in memory.
Please reword:
... one or more segment addresses, section base addresses, or SVR4
linker parameters. These describe where the library was loaded into
memory.
> +depend on the library's link-time base addresses. For SVR4 systems
> +are reported parameters @{lm} with address of @code{struct link_map}
> +used for TLS (Thread Local Storage) access, @code{l_addr} specifying
> +bias of the mapped memory address minus the prelinked base address
> +and also @code{l_ld} which is memory address of the @code{PT_DYNAMIC}
> +segment. SVR4 systems additionally specify @code{struct link_map}
> +address of the main executable in the @code{<library-list>} element.
This is too much for a single sentence. I suggest an itemized list
instead:
For SVR4 systems, the following parameters are reported:
@itemize @minus
@item
@code{lm} with address of @code{struct link_map} used ...
@item
@code{l_ld}, which is memory address of ...
...
@end itemize
And btw, are we sure that sayin "SVR4 systems" is enough to
unambiguously identify those systems? How about at least a partial
list in parentheses?
> + if (*phdr_memaddr == 0 || *num_phdr == 0)
> + {
> + warning ("Unexpected missing AT_PHDR and/or AT_PHNUM: "
> + "phdr_memaddr = %ld, phdr_num = %d",
No _() ? Doesn't gdbserver support translations of messages?
next prev parent reply other threads:[~2011-10-04 6:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 21:55 Jan Kratochvil
2011-10-04 6:11 ` Eli Zaretskii [this message]
2011-10-18 17:49 ` Messages localization in gdbserver [Re: [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2] Jan Kratochvil
2011-10-06 19:09 ` [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2 Pedro Alves
2011-10-21 11:05 ` Jan Kratochvil
2011-10-21 13:32 ` Pedro Alves
2011-11-03 21:30 ` [patch] Implement qXfer:libraries-svr4 for Linux/gdbserver #4 Jan Kratochvil
2011-12-02 22:33 ` [commit] " Jan Kratochvil
2011-12-03 17:03 ` Doug Evans
2011-12-03 18:34 ` [commit] Fix compilation --without-expat [Re: [commit] [patch] Implement qXfer:libraries-svr4 for Linux/gdbserver #4] Jan Kratochvil
2011-10-10 2:44 ` [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2 Daniel Jacobowitz
2011-10-12 20:22 ` 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=E1RAyE5-0006y9-Bz@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ppluzhnikov@google.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