From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org,
jan.kratochvil@redhat.com, patches@linaro.org
Subject: Re: [rfc v2, rfa-doc] Disable address space randomization with remote targets
Date: Wed, 05 Oct 2011 18:44:00 -0000 [thread overview]
Message-ID: <83y5wzgtxz.fsf@gnu.org> (raw)
In-Reply-To: <201110051832.p95IWuVb029968@d06av02.portsmouth.uk.ibm.com>
> Date: Wed, 5 Oct 2011 20:32:56 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com (Jan Kratochvil), patches@linaro.org
>
> -The virtual address space randomization is implemented only on @sc{gnu}/Linux.
> -It protects the programs against some kinds of security attacks. In these
> +On targets where it is available, virtual address space randomization
> +protects the programs against some kinds of security attacks. In these
^^^^^^^^^^
"certain kinds"
> +Some target operating systems will randomize the inferior process'
> +virtual address space as a security feature, but provide a feature
It is better to say "randomize the virtual address space of the
inferior process", then you won't have the "issue" with "ss's".
> +to disable such randomization, e.g. to allow for a more deterministic
^^^^
"e.g.@:", to hint TeX not to typeset this as an end of a sentence.
The documentation part is okay with these changes.
next prev parent reply other threads:[~2011-10-05 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 16:56 [rfc, gdbserver] Disable address space randomization Ulrich Weigand
2011-09-29 18:12 ` Jan Kratochvil
2011-09-30 15:08 ` Ulrich Weigand
2011-09-30 19:32 ` Pedro Alves
2011-10-05 18:33 ` [rfc v2, rfa-doc] Disable address space randomization with remote targets Ulrich Weigand
2011-10-05 18:44 ` Eli Zaretskii [this message]
2011-10-07 12:08 ` Ulrich Weigand
2011-10-05 20:10 ` Tom Tromey
2011-10-06 13:25 ` Pedro Alves
2011-10-07 12:15 ` Ulrich Weigand
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=83y5wzgtxz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=patches@linaro.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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