From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 1/2] Correct the type of sigFOO_token
Date: Sun, 21 Oct 2012 02:59:00 -0000 [thread overview]
Message-ID: <1350788330-7135-2-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <1350788330-7135-1-git-send-email-yao@codesourcery.com>
Hi,
These signal tokens can be defined in type 'struct
async_signal_handler *' instead of 'void *'. This patch is do this.
gdb:
2012-10-21 Yao Qi <yao@codesourcery.com>
* event-top.c (sigint_token, sighup_token): Replace 'void *' with
'static struct async_signal_handler *'.
(sighup_token, sigquit_token, sigstp_token): Likewise.
---
gdb/event-top.c | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/gdb/event-top.c b/gdb/event-top.c
index 4f3363c..1e0626a 100644
--- a/gdb/event-top.c
+++ b/gdb/event-top.c
@@ -123,16 +123,16 @@ int input_fd;
handlers mark these functions as ready to be executed and the event
loop, in a later iteration, calls them. See the function
invoke_async_signal_handler. */
-void *sigint_token;
+static struct async_signal_handler *sigint_token;
#ifdef SIGHUP
-void *sighup_token;
+static struct async_signal_handler *sighup_token;
#endif
#ifdef SIGQUIT
-void *sigquit_token;
+static struct async_signal_handler *sigquit_token;
#endif
-void *sigfpe_token;
+static struct async_signal_handler *sigfpe_token;
#ifdef STOP_SIGNAL
-void *sigtstp_token;
+static struct async_signal_handler *sigtstp_token;
#endif
/* Structure to save a partially entered command. This is used when
--
1.7.7.6
next prev parent reply other threads:[~2012-10-21 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 2:59 [obv 0/2] Minor cleanup in event-top.c Yao Qi
2012-10-21 2:59 ` [PATCH 2/2] Remove mark_async_signal_handler_wrapper Yao Qi
2012-10-22 14:23 ` Tom Tromey
2012-10-21 2:59 ` Yao Qi [this message]
2012-10-22 14:21 ` [PATCH 1/2] Correct the type of sigFOO_token Tom Tromey
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=1350788330-7135-2-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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