From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Paul Koning <paulkoning@comcast.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Disable address space randomization for a test
Date: Mon, 30 Jul 2018 19:49:00 -0000 [thread overview]
Message-ID: <f22d448fe232b344e28713d06157a6fe@polymtl.ca> (raw)
In-Reply-To: <20180730190155.GF3155@embecosm.com>
On 2018-07-30 15:01, Andrew Burgess wrote:
>> Does that turn off address randomization? The keyword implies the
>> opposite (double negative, so "disable... off" means "turn on").
>
> That's a very good question... now I just have to figure out why my
> incorrect patch fixed the problem I was seeing.... watch this space...
GDB usually disables address randomization by default, so I was also
wondering why this would be needed. Do you have a scenario where GDB
doesn't disable it by default?
Simon
next prev parent reply other threads:[~2018-07-30 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 18:50 Andrew Burgess
2018-07-30 18:56 ` Paul Koning
2018-07-30 19:02 ` Andrew Burgess
2018-07-30 19:49 ` Simon Marchi [this message]
2018-07-31 12:47 ` Andrew Burgess
2018-07-31 13:32 ` Simon Marchi
2018-07-31 14:23 ` Tom Tromey
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=f22d448fe232b344e28713d06157a6fe@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=paulkoning@comcast.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).