From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Ulrich Weigand" <uweigand@de.ibm.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
patches@linaro.org
Subject: Re: [rfc, gdbserver] Disable address space randomization
Date: Fri, 30 Sep 2011 19:32:00 -0000 [thread overview]
Message-ID: <201109301715.06928.pedro@codesourcery.com> (raw)
In-Reply-To: <201109301317.p8UDH8s5023472@d06av02.portsmouth.uk.ibm.com>
On Friday 30 September 2011 14:17:08, Ulrich Weigand wrote:
> As to the remote command for extended mode, I'm not completely sure what
> the best way to trigger that from within GDB should be. Should we promote
> "set disable-randomization" from being a Linux-specific command to the
> generic level, and have its value passed to the target by remote.c?
Yes. This came up recently for (native) Darwin/OSX too. That target now
always disables ASR, and it'd be good to give the user the option
to re-enable it.
> Or else a new QDisableRandomization packet that affects all subsequent
> vRun commands?
I think that's the best. It's kind of similar to "set disconnected-tracing"
and "set circular-trace-buffer".
--
Pedro Alves
next prev parent reply other threads:[~2011-09-30 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 16:56 Ulrich Weigand
2011-09-29 18:12 ` Jan Kratochvil
2011-09-30 15:08 ` Ulrich Weigand
2011-09-30 19:32 ` Pedro Alves [this message]
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
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=201109301715.06928.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=patches@linaro.org \
--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