From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa] Always define all of TARGET_SIGNAL_*
Date: Wed, 27 Feb 2002 19:11:00 -0000 [thread overview]
Message-ID: <20020227221148.A30753@nevyn.them.org> (raw)
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.
OK?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
2002-02-27 Daniel Jacobowitz <drow@mvista.com>
* defs.h (enum target_signal): Do not let conditional compilation
affect signal numbers.
Index: defs.h
===================================================================
RCS file: /cvs/src/src/gdb/defs.h,v
retrieving revision 1.81
diff -u -p -r1.81 defs.h
--- defs.h 2002/02/26 03:29:55 1.81
+++ defs.h 2002/02/28 03:09:09
@@ -404,7 +404,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,
@@ -412,7 +411,7 @@ enum target_signal
TARGET_EXC_EMULATION,
TARGET_EXC_SOFTWARE,
TARGET_EXC_BREAKPOINT,
-#endif
+
TARGET_SIGNAL_INFO,
/* Some signal we don't know about. */
next reply other threads:[~2002-02-28 3:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 19:11 Daniel Jacobowitz [this message]
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
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=20020227221148.A30753@nevyn.them.org \
--to=drow@mvista.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