Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Michael Snyder <msnyder@redhat.com>, Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/SPARC-branch] Make call dummies on non-executable stack work
Date: Wed, 15 Oct 2003 23:06:00 -0000	[thread overview]
Message-ID: <1031015230615.ZM23202@localhost.localdomain> (raw)
In-Reply-To: Michael Snyder <msnyder@redhat.com> "Re: [PATCH/SPARC-branch] Make call dummies on non-executable stack work" (Oct 15,  3:28pm)

On Oct 15,  3:28pm, Michael Snyder wrote:

> Mark Kettenis wrote:
> > The attached patch makes call dummies on a non-executable stack
> > working.  I checked this in on my SPARC branch.  What do people think
> > about checking this in on mainline?  I don't think this will get much
> > exposure on the branch.
> 
> I guess the only way you would get a false positive here
> would be if you took a SEGV while executing a breakpoint trap.
> I *guess* that seems unlikely -- but I wonder if there's a
> pathological case, or if one might see this happening while
> porting gdb to a new target, an immature sim, or something?
> 
> Is there a gotcha, for instance, for VLIW machines?
> Might execute the trap, and another instruction simultaneously?
> Kevin?

I don't think there's any problem for IA-64.  For FR-V, this might
indeed be a gotcha.  Unfortunately, although I've looked at the
FR-V architecture manual, I'm unable to tell if this'd be a problem
or not.

(Sorry for the less than helpful reply...)

Kevin


      reply	other threads:[~2003-10-15 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 19:57 Mark Kettenis
2003-10-15 20:08 ` Daniel Jacobowitz
2003-10-15 22:28 ` Michael Snyder
2003-10-15 23:06   ` Kevin Buettner [this message]

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=1031015230615.ZM23202@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=msnyder@redhat.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