From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, drow@false.org, ppluzhnikov@google.com
Subject: Re: [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #3
Date: Tue, 18 Oct 2011 21:26:00 -0000 [thread overview]
Message-ID: <83fwiqui3p.fsf@gnu.org> (raw)
In-Reply-To: <20111018205220.GC31533@host1.jankratochvil.net>
> Date: Tue, 18 Oct 2011 22:52:20 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Daniel Jacobowitz <drow@false.org>, Paul Pluzhnikov <ppluzhnikov@google.com>
>
> +For SVR4 systems, a single segment is reported. For SVR4 system the
> +@code{library-list} element should have @code{main-lm} attribute with address
> +of @code{struct link_map} used for the main executable.
Can we reword this not to say "For SVR4 systems" twice in a row?
Okay with that change.
Thanks.
next prev parent reply other threads:[~2011-10-18 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 21:04 Jan Kratochvil
2011-10-18 21:26 ` Eli Zaretskii [this message]
2011-10-18 21:53 ` 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=83fwiqui3p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.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