Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Thu, 29 Jun 2000 18:17:18 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: [Update] Re: GDB on Win2k doesn't work for me. Message-ID: <20000629181718.A8571@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <20000626163802.A3414@cygnus.com> <20000626181747.A5675@cygnus.com> <20000627004702.A15783@cygnus.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 02:43:48PM -0400 On Thu, Jun 29, 2000 at 02:43:48PM -0400, Paul Stodghill wrote: >> I found the problem. I uninstalled Innoculin and gdb suddenly worked again. > >I spoke too soon. Innoculin wasn't the problem. > >GDB does not work when I log into my computer while it is connected to the >network. GDB does work when I log into my computer without it being >connected to the network, but reconnect it once it I am logged in. > >RECIPE FOR GDB FAILURE >====================== >1. With computer connected to the LAN, log in. >2. Start gdb with a program, and run the program, > >milhouse% gcc -g -o foo.exe foo.c >milhouse% gdb -nw foo.exe >GNU gdb 5.0 >Copyright 2000 Free Software Foundation, Inc. >GDB is free software, covered by the GNU General Public License, and you are >welcome to change it and/or distribute copies of it under certain conditions. >Type "show copying" to see the conditions. >There is absolutely no warranty for GDB. Type "show warranty" for details. >This GDB was configured as "i686-pc-cygwin"... >(gdb) run >Starting program: /home/stodghil/localhome/tmp/foo.exe >gdb: unknown target exception 0x000006d1 at 0x77e89b01 > >Program received signal ?, Unknown signal. >0x77e89b01 in ?? () >(gdb) > >RECIPE FOR GDB SUCCESS >====================== >1. Disconnect the computer from the LAN. >2. Log in. >3. Once the machine has finished logging you in, reconnect the network. >4. Start gdb with a program, and run the program, > >milhouse% gcc -g -o foo.exe foo.c >milhouse% gdb -nw foo.exe >GNU gdb 5.0 >Copyright 2000 Free Software Foundation, Inc. >GDB is free software, covered by the GNU General Public License, and you are >welcome to change it and/or distribute copies of it under certain conditions. >Type "show copying" to see the conditions. >There is absolutely no warranty for GDB. Type "show warranty" for details. >This GDB was configured as "i686-pc-cygwin"... >(gdb) run >Starting program: /home/stodghil/localhome/tmp/foo.exe >Hello, world. > >Program exited with code 016. >(gdb) > >--------------------------------------------------------------------------- >Other information: >o My machine is in a Windows domain, not a workgroup >o I have verified that this problem also occurs on a different machine in a > different Windows domain. >o Unmapping all of the network drives didn't seem to make a difference in > either case. >o If I log in as a LOCAL user (ie, MILHOUSE\Administrator), while the > computer is connected to the network, GDB works! > >Any ideas? Yes. I've given two suggestions that I haven't seen followed up on. 1) Try 'set debugexceptions' 2) Debug gdb.exe and figure out where and why this is failing. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com