Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 29 Jun 2000 19:19:18 -0400 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: [Update] Re: GDB on Win2k doesn't work for me. Message-ID: <20000629191918.B8833@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <20000626163802 DOT A3414 AT cygnus DOT com> <20000626181747 DOT A5675 AT cygnus DOT com> <20000627004702 DOT A15783 AT cygnus DOT com> <20000629181718 DOT A8571 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from stodghil@CS.Cornell.EDU on Thu, Jun 29, 2000 at 07:00:54PM -0400 On Thu, Jun 29, 2000 at 07:00:54PM -0400, Paul Stodghill wrote: >>>Any ideas? >> >>Yes. I've given two suggestions that I haven't seen followed up on. >> >>1) Try 'set debugexceptions' > >Right, forgot about that... > >I tried this and it doesn't fix the problem. It isn't supposed to fix the problem. It was supposed to provide additional debugging output. >> 2) Debug gdb.exe and figure out where and why this is failing. > >I'm not sure how I can debug gdb without a working gdb, but I'm trying to >improvise... > >I just tried running strace on gdb in both scenarios. strace is not going to be useful here. Someone suggested that B20.1 versions of gdb worked. Otherwise, the judicious use of printf's in win32-nat.c is the only other thing I can think of. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com