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
Date: Tue, 18 Jul 2000 12:29:49 +0100
Message-ID: <4180-Tue18Jul2000122949+0100-starksb@ebi.ac.uk>
X-Mailer: emacs 20.6.1 (via feedmail 9-beta-7 I);
	VM 6.75 under Emacs 20.6.1
From: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Chris Faylor <cgf AT cygnus DOT com>
CC: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: GDB signal handling not working (stop, print, nopass, etc)
In-Reply-To: <20000707223746.A1030@cygnus.com>
References: <200007080230 DOT WAA15177 AT qnx DOT com>
	<20000707223746 DOT A1030 AT cygnus DOT 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 AT sourceware DOT cygnus DOT com