This is the mail archive of the gdb-patches@sourceware.cygnus.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: More signal-related patches for GDB



Should we use SIG_ERR instead of __djgpp_traceback_exit?  If so, can
it be universal, so that there isn't any host-specific code here?

> Date: Sun, 27 Jun 1999 19:00:13 +0300 (IDT)
> From: Eli Zaretskii <eliz@is.elta.co.il>
> X-Sender: eliz@is
> cc: Robert Hoehne <robert.hoehne@gmx.net>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> 
> 1999-06-26  Eli Zaretskii  <eliz@is.elta.co.il>
> 
> 	* maint.c (maintenance_dump_me) [__DJGPP__]: Make it so SIGQUIT
> 	produces traceback, the equivalent of a core dump.
> 
> *** ./gdb/maint.c~0	Fri Jun 13 17:30:06 1997
> --- ./gdb/maint.c	Thu May 20 21:33:42 1999
> *************** maintenance_dump_me (args, from_tty)
> *** 99,105 ****
> --- 99,110 ----
>   {
>     if (query ("Should GDB dump core? "))
>       {
> + #ifdef __DJGPP__
> +       /* SIG_DFL for SIGQUIT is the same as SIG_IGN.  */
> +       signal (SIGQUIT, __djgpp_traceback_exit);
> + #else
>         signal (SIGQUIT, SIG_DFL);
> + #endif
>         kill (getpid (), SIGQUIT);
>       }
>   }
> 

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]