Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: Possible future NX ON_STACk regression  Re: [patch 3/3] Use ON_STACK for i386/amd64 (gdb2495.exp regression)
Date: Mon, 18 Jun 2012 08:09:00 -0000	[thread overview]
Message-ID: <20120618080907.GA24971@host2.jankratochvil.net> (raw)
In-Reply-To: <20120613155103.GC26214@host2.jankratochvil.net>

On Wed, 13 Jun 2012 17:51:03 +0200, Jan Kratochvil wrote:
> +  set_gdbarch_call_dummy_location (gdbarch, ON_STACK);

In https://bugzilla.redhat.com/show_bug.cgi?id=832534 Nathan Sidwell reports
that inferior calls segfault with inferior non-executable stack and Fedora GDB
already containing this patch.

I do not have it reproducible, I guess it may be CPU firmware dependent.


Regards,
Jan


  reply	other threads:[~2012-06-18  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 15:51 Jan Kratochvil
2012-06-18  8:09 ` Jan Kratochvil [this message]
2012-06-18 14:21   ` Possible future NX ON_STACk regression " Jan Kratochvil
2012-06-18 14:51     ` Mark Kettenis
2012-06-18 17:32       ` [commit] " 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=20120618080907.GA24971@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@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