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 From: Chris Faylor Date: Tue, 11 Jul 2000 20:54:24 -0400 To: "'cygwin@sourceware.cygnus.com'" Subject: Re: GDB on Win2k doesn't work for me. Message-ID: <20000711205424.A31266@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: "'cygwin@sourceware.cygnus.com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from pepperd@climax.co.uk on Tue, Jul 11, 2000 at 09:31:42AM +0100 On Tue, Jul 11, 2000 at 09:31:42AM +0100, Damyan Pepper wrote: >I too suffer from the Unknown Target Exception problem. I am running >gdb-20000610.tgz. > >> On 27 Jun 2000, Paul Stodghill wrote: >> >> > I found the problem. I uninstalled Innoculin and gdb >> suddenly worked again. > >Following that lead I figured that xemacs could be interfering -- I've had >problems before with xemacs coexisting with virus programs. It wasn't. :-( > >Anyway, some more, probably useless output: > >(gdb) set debugexceptions >(gdb) run >Starting program: /home/noah/a.exe >gdb: Target exception BREAKPOINT at 0x77f9f9df >gdb: unknown target exception 0x000006d1 at 0x77e89b01 > >Program received signal ?, Unknown signal. >0x77e89b01 in ?? () > > > >What sort of information might be of help to someone who has the ability and >will to try and fix this? Debug gdb (this is a recording). Use an older version of gdb if the one you have isn't working. Or, insert printfs at strategic locations in win32-nat.c. It's possible that you might even be able to just continue through the above exception. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com