Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: gdb@sources.redhat.com
Subject: [RFC] Non-executable stack on SPARC
Date: Sun, 25 Jan 2004 23:50:00 -0000	[thread overview]
Message-ID: <200401252350.i0PNoB1O021806@elgar.kettenis.dyndns.org> (raw)

A while ago, I established that getting inferior function calls on
SPARC working with a non-executable stack is remarkably simple.  Just
acknowledging that breakpoint instructions may cause SIGSEGV, as per
the attached patch, is enough.  However, some people were afraid that
blindly applying this patch might cause some problems on other
targets.  I think there are two alternatives:

1. Only check for SIGSEGV if the target in question uses "ON_STACK"
   for its call_dummy_location.

2. Add a new method to the architecture vector to check whether a
   particular signal may have been the result of a breakpoint
   instruction.  Suggested name & signature:

   int breakpoint_signal_p (struct gdbarch *gdbarch, int signal)

Preferences?

I'd like to get this sorted before 6.1, since OpenBSD/sparc has a
non-executable stack, and some people are running SPARC Solaris with a
non-executable stack too.

Mark


Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.122
diff -u -p -r1.122 infrun.c
--- infrun.c 25 Nov 2003 16:01:36 -0000 1.122
+++ infrun.c 25 Jan 2004 23:37:01 -0000
@@ -1864,6 +1864,7 @@ handle_inferior_event (struct execution_
   if (stop_signal == TARGET_SIGNAL_TRAP
       || (breakpoints_inserted &&
 	  (stop_signal == TARGET_SIGNAL_ILL
+	   || stop_signal == TARGET_SIGNAL_SEGV
 	   || stop_signal == TARGET_SIGNAL_EMT))
       || stop_soon == STOP_QUIETLY
       || stop_soon == STOP_QUIETLY_NO_SIGSTOP)


             reply	other threads:[~2004-01-25 23:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 23:50 Mark Kettenis [this message]
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

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=200401252350.i0PNoB1O021806@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb@sources.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