Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 18 Jul 2000 09:00:59 -0400 From: Chris Faylor To: David Starks-Browning Cc: cygwin@sourceware.cygnus.com Subject: Re: GDB signal handling not working (stop, print, nopass, etc) Message-ID: <20000718090059.C5488@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: David Starks-Browning , cygwin@sourceware.cygnus.com References: <200007080230.WAA15177@qnx.com> <20000707223746.A1030@cygnus.com> <4180-Tue18Jul2000122949+0100-starksb@ebi.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4180-Tue18Jul2000122949+0100-starksb@ebi.ac.uk>; from starksb@ebi.ac.uk on Tue, Jul 18, 2000 at 12:29:49PM +0100 On Tue, Jul 18, 2000 at 12:29:49PM +0100, David Starks-Browning wrote: >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. > >Is this FAQ fodder? Definitely! cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com