Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: Allow for systems that do not define SIGQUIT/SIGPIPE
Date: Wed, 16 Mar 2005 16:33:00 -0000	[thread overview]
Message-ID: <200503161633.j2GGX3Fl020753@sethra.codesourcery.com> (raw)


Windows does not have SIGQUIT or SIGPIPE.  

Tested on x86_64-unknown-linux-gnu.

OK?

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

2005-03-16  Mark Mitchell  <mark@codesourcery.com>

	* event-top.c (async_init_signals): Allow for systems that do not
	define SIGQUIT.
	* ser-tcp.c (net_open): Allow for systems that do not have SIGPIPE.

Index: event-top.c
===================================================================
RCS file: /cvs/src/src/gdb/event-top.c,v
retrieving revision 1.39
diff -c -5 -p -r1.39 event-top.c
*** event-top.c	12 Feb 2005 00:39:19 -0000	1.39
--- event-top.c	16 Mar 2005 16:07:44 -0000
*************** async_init_signals (void)
*** 893,902 ****
--- 893,903 ----
       to the inferior and breakpoints will be ignored.  */
  #ifdef SIGTRAP
    signal (SIGTRAP, SIG_DFL);
  #endif
  
+ #ifdef SIGQUIT
    /* If we initialize SIGQUIT to SIG_IGN, then the SIG_IGN will get
       passed to the inferior, which we don't want.  It would be
       possible to do a "signal (SIGQUIT, SIG_DFL)" after we fork, but
       on BSD4.3 systems using vfork, that can affect the
       GDB process as well as the inferior (the signal handling tables
*************** async_init_signals (void)
*** 904,913 ****
--- 905,915 ----
       a handler for SIGQUIT, when we call exec it will set the signal
       to SIG_DFL for us.  */
    signal (SIGQUIT, handle_sigquit);
    sigquit_token =
      create_async_signal_handler (async_do_nothing, NULL);
+ #endif
  #ifdef SIGHUP
    if (signal (SIGHUP, handle_sighup) != SIG_IGN)
      sighup_token =
        create_async_signal_handler (async_disconnect, NULL);
    else
Index: ser-tcp.c
===================================================================
RCS file: /cvs/src/src/gdb/ser-tcp.c,v
retrieving revision 1.17
diff -c -5 -p -r1.17 ser-tcp.c
*** ser-tcp.c	11 Feb 2005 04:06:04 -0000	1.17
--- ser-tcp.c	16 Mar 2005 16:07:44 -0000
*************** net_open (struct serial *scb, const char
*** 184,196 ****
--- 184,198 ----
        tmp = 1;
        setsockopt (scb->fd, IPPROTO_TCP, TCP_NODELAY,
  		  (char *)&tmp, sizeof (tmp));
      }
  
+ #ifdef SIGPIPE
    /* If we don't do this, then GDB simply exits
       when the remote side dies.  */
    signal (SIGPIPE, SIG_IGN);
+ #endif
  
    return 0;
  }
  
  static void


             reply	other threads:[~2005-03-16 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 16:33 Mark Mitchell [this message]
2005-03-16 16:43 ` Daniel Jacobowitz
2005-03-16 16:51   ` Mark Mitchell
2005-03-16 16:52     ` Daniel Jacobowitz
2005-03-16 17:08       ` Mark Mitchell
2005-03-16 16:53   ` Mark Mitchell

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=200503161633.j2GGX3Fl020753@sethra.codesourcery.com \
    --to=mark@codesourcery.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