This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: GDB signal handling not working (stop, print, nopass, etc)
- To: Chris Faylor <cgf at cygnus dot com>
- Subject: Re: GDB signal handling not working (stop, print, nopass, etc)
- From: David Starks-Browning <starksb at ebi dot ac dot uk>
- Date: Tue, 18 Jul 2000 12:29:49 +0100
- CC: cygwin at sourceware dot cygnus dot com
- References: <200007080230.WAA15177@qnx.com><20000707223746.A1030@cygnus.com>
On Friday 7 Jul 00, Chris Faylor writes:
> On Fri, Jul 07, 2000 at 10:27:45PM -0400, Max Feil wrote:
> >Hi folks. I am desperate to get the "handle" command of gdb working under
> >Cygwin. Try as I might, I can't get gdb to stop, print, or "nopass"
> >signals like SIGUSR1 or SIGHUP to the process being debugged.
>
> Signal handling only works with Windows-type signals currently. SIGINT
> may work, SIGFPE may work, SIGSEGV definitely does.
>
> I tried to add some recognition of cygwin's signals a while ago but it
> never worked right and I never got too far with it.
>
> Sorry, but there is only minimal signal handling support in gdb currently.
>
> cgf
Is this FAQ fodder?
David
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com