Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] SIGTERM handler
Date: Wed, 16 Nov 2005 19:29:00 -0000	[thread overview]
Message-ID: <437B6374.1@st.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]

Hi,

This patch adds a handler for SIGTERM.

The main purpose is to ensure that GDB quit through quit_force() and
therefore properly disconnects from the target. This is quite important
for our target interface and should do no harm for anybody else's.

It also ensures that --return-child-result works when GDB exits this way.

Thanks

Andrew Stubbs

[-- Attachment #2: sigterm.patch --]
[-- Type: text/plain, Size: 1704 bytes --]

2005-11-16  Andrew Stubbs  <andrew.stubbs@st.com>

	* event-top.h (async_init_signals): Add SIGTERM handler.
	(handle_sigterm): New function.
	* event-top.h (handle_sigterm): New prototype.

Index: src/gdb/event-top.c
===================================================================
--- src.orig/gdb/event-top.c	2005-11-09 12:02:37.000000000 +0000
+++ src/gdb/event-top.c	2005-11-09 12:03:22.000000000 +0000
@@ -892,6 +892,7 @@ async_init_signals (void)
   signal (SIGINT, handle_sigint);
   sigint_token =
     create_async_signal_handler (async_request_quit, NULL);
+  signal (SIGTERM, handle_sigterm);
 
   /* If SIGTRAP was set to SIG_IGN, then the SIG_IGN will get passed
      to the inferior and breakpoints will be ignored.  */
@@ -964,6 +965,15 @@ handle_sigint (int sig)
     mark_async_signal_handler_wrapper (sigint_token);
 }
 
+/* Quit GDB if SIGTERM is received.
+   GDB would quit anyway, but this way it will clean up properly.  */
+void
+handle_sigterm (int sig)
+{
+  signal (sig, handle_sigterm);
+  quit_force ((char *) 0, stdin == instream);
+}
+
 /* Do the quit. All the checks have been done by the caller. */
 void
 async_request_quit (gdb_client_data arg)
Index: src/gdb/event-top.h
===================================================================
--- src.orig/gdb/event-top.h	2003-04-12 18:41:25.000000000 +0100
+++ src/gdb/event-top.h	2005-11-09 12:02:44.000000000 +0000
@@ -97,6 +97,7 @@ extern void handle_stop_sig (int sig);
 #endif
 #endif
 extern void handle_sigint (int sig);
+extern void handle_sigterm (int sig);
 extern void pop_prompt (void);
 extern void push_prompt (char *prefix, char *prompt, char *suffix);
 extern void gdb_readline2 (void *client_data);

             reply	other threads:[~2005-11-16 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 19:29 Andrew STUBBS [this message]
2005-11-25 18:06 ` Andrew STUBBS
2005-11-25 18:11 ` Daniel Jacobowitz
2005-11-25 20:13   ` Andrew STUBBS

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=437B6374.1@st.com \
    --to=andrew.stubbs@st.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