Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Fri, 7 Jul 2000 22:37:46 -0400
To:	cygwin AT sources DOT redhat DOT com
Subject:	Re: GDB signal handling not working (stop, print, nopass, etc)
Message-ID:	<20000707223746.A1030@cygnus.com>
Mail-Followup-To:	cygwin AT sources DOT redhat DOT com
References:	<200007080230 DOT WAA15177 AT qnx DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2i
In-Reply-To:	<200007080230.WAA15177@qnx.com>; from mfeil@qnx.com on Fri, Jul 07, 2000 at 10:27:45PM -0400

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

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -