public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17785] GDB ignores "disable-randomization" setting once its set to off once
Date: Mon, 05 Jan 2015 17:13:00 -0000	[thread overview]
Message-ID: <bug-17785-4717-tJkEMIxMnc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17785-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17785

--- Comment #3 from Doug Evans <xdje42 at gmail dot com> ---
(In reply to dman79 from comment #2)
> Reproducing the problem is simple  gdb myprogram
> show disable-randomization
> set disable-randomization on
> quit
> 
> gdb myprogram
> b *main
> r
> x/x $esp
> r
> x/x $esp
> show disable-randomization
> 
> which will be on but $esp will be randomized on each single run.

Did you mean "set disable-randomization" off in the above example?

Plus, are you saying that enabling randomization *** in a separate ***
gdb session then enabled randomization for all subsequent gdb sessions?
If so, that's a kernel bug.

I still can't reproduce the problem.
Let's first pin down your repro.
Can you paste an unedited session log, starting from the shell command that
launches gdb?

And, on the off chance (seems unlikely, but who knows), what's your kernel
version?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-01-05 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 15:34 [Bug gdb/17785] New: " dman79 at gmail dot com
2015-01-03 18:14 ` [Bug gdb/17785] " xdje42 at gmail dot com
2015-01-05  7:22 ` dman79 at gmail dot com
2015-01-05 17:13 ` xdje42 at gmail dot com [this message]
2022-03-06 17:49 ` tromey at sourceware dot org

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=bug-17785-4717-tJkEMIxMnc@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).