From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] Non-executable stack on SPARC
Date: Mon, 02 Feb 2004 18:27:00 -0000 [thread overview]
Message-ID: <401E968C.1020908@gnu.org> (raw)
In-Reply-To: <200402011754.i11HsTdQ000570@elgar.kettenis.dyndns.org>
> Assuming that for VLIW gdb replaces the entire instruction bundle with a
> breakpoint, a breakpoint instruction can only ever generate a sigtrap
> (et.al.) (if executed) or sigsegv (if not accessible) so provided there
> is a breakpoint at the PC I don't think there is any possability of
> confusion (but again ignore decr pc after break :-).
>
> So does this mean you're convinced that we can add SIGSEGV to the list
> currently consisting of SIGILL and SIGEMT unconditionally? I haven't
> seen any ill effects on IA-32 and AMD64 (which are decr pc after
> break). I'll happilly check in the origional patch in mainline too.
We've found no evidence to the contrary - if something later breaks we
can add that to the testsuite.
Andrew
prev parent reply other threads:[~2004-02-02 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 23:50 Mark Kettenis
2004-01-25 23:59 ` Daniel Jacobowitz
2004-01-26 6:51 ` Eli Zaretskii
2004-01-26 6:51 ` Eli Zaretskii
2004-01-26 12:42 ` Mark Kettenis
2004-01-27 8:16 ` Eli Zaretskii
2004-02-01 17:48 ` Mark Kettenis
2004-02-01 20:13 ` Eli Zaretskii
2004-02-02 18:37 ` Andrew Cagney
2004-01-26 16:21 ` Andrew Cagney
2004-01-27 8:00 ` Eli Zaretskii
2004-02-01 17:54 ` Mark Kettenis
2004-02-02 18:27 ` Andrew Cagney [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=401E968C.1020908@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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