Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Always define all of TARGET_SIGNAL_*
Date: Sun, 10 Mar 2002 16:20:00 -0000	[thread overview]
Message-ID: <20020310192038.A14083@nevyn.them.org> (raw)
In-Reply-To: <3C7E6634.4010209@cygnus.com>

On Thu, Feb 28, 2002 at 12:17:40PM -0500, Andrew Cagney wrote:
> >On Thu, Feb 28, 2002 at 09:57:48AM -0500, Andrew Cagney wrote:
> >
> >>>I've been meaning to fix this since I noticed it last summer.  These 
> >>>numbers
> >>>are part of the remote protocol.  While I think the last ones are never 
> >>>sent
> >>>over the wire, they could be (with the exception of TARGET_SIGNAL_LAST 
> >>>which
> >>>is -not- part of the protocol, as I understand it).  Having them jump 
> >>>around
> >>>is bad.
> >
> >>
> >>Wasn't this enum going to be moved to signals.h?
> >
> >
> >I think so, but I didn't see any pressing reason to.  If you want, I
> >can do that.
> >
> >OK otherwise?
> 
> I'd leave it until after things branch and then fix it properly in the 
> trunk.

Now that we've got a "gdb/signals.h", there's a place to fix this
properly in the trunk.  How does this patch look?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

2002-03-10  Daniel Jacobowitz  <drow@mvista.com>

        * signals.h: Update comments.
	(enum target_signal): Remove conditional compilation around
	Mach-specific signals.

Index: signals.h
===================================================================
RCS file: /cvs/src/src/include/gdb/signals.h,v
retrieving revision 1.1
diff -u -p -r1.1 signals.h
--- signals.h	2002/03/11 00:01:11	1.1
+++ signals.h	2002/03/11 00:20:15
@@ -32,7 +32,8 @@
    Since these numbers have actually made it out into other software
    (stubs, etc.), you mustn't disturb the assigned numbering.  If you
    need to add new signals here, add them to the end of the explicitly
-   numbered signals.
+   numbered signals, at the comment marker.  Add them unconditionally,
+   not within any #if or #ifdef.
 
    This is based strongly on Unix/POSIX signals for several reasons:
    (1) This set of signals represents a widely-accepted attempt to
@@ -208,7 +209,6 @@ enum target_signal
     TARGET_SIGNAL_REALTIME_126,
     TARGET_SIGNAL_REALTIME_127,
 
-#if defined(MACH) || defined(__MACH__)
     /* Mach exceptions */
     TARGET_EXC_BAD_ACCESS,
     TARGET_EXC_BAD_INSTRUCTION,
@@ -216,7 +216,7 @@ enum target_signal
     TARGET_EXC_EMULATION,
     TARGET_EXC_SOFTWARE,
     TARGET_EXC_BREAKPOINT,
-#endif
+
     TARGET_SIGNAL_INFO,
 
     /* Some signal we don't know about.  */
@@ -225,6 +225,8 @@ enum target_signal
     /* Use whatever signal we use when one is not specifically specified
        (for passing to proceed and so on).  */
     TARGET_SIGNAL_DEFAULT,
+
+    /* If you are adding a new signal, add it just above this comment.  */
 
     /* Last and unused enum value, for sizing arrays, etc.  */
     TARGET_SIGNAL_LAST


  parent reply	other threads:[~2002-03-11  0:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 19:11 Daniel Jacobowitz
2002-02-28  6:57 ` Andrew Cagney
2002-02-28  8:51   ` Daniel Jacobowitz
2002-02-28  9:17     ` Andrew Cagney
2002-02-28  9:44       ` Daniel Jacobowitz
2002-03-10 16:20       ` Daniel Jacobowitz [this message]
2002-03-11 18:33         ` Andrew Cagney
2002-03-11 18:49           ` Daniel Jacobowitz
2002-03-11 20:01             ` Andrew Cagney
2002-03-16 18:27               ` Daniel Jacobowitz
2002-03-16 18:38                 ` Andrew Cagney
2002-05-09 15:22                   ` Daniel Jacobowitz

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=20020310192038.A14083@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@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