Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
To: cygwin AT sourceware DOT cygnus DOT com, Adam Schlegel <aceschle AT thinkage DOT ca>
Subject: [Update] Re: GDB on Win2k doesn't work for me.
References: <20000626163802 DOT A3414 AT cygnus DOT com>
	<Pine DOT LNX DOT 4 DOT 10 DOT 10006261723090 DOT 18849-100000 AT mailhost DOT thinkage DOT ca>
	<20000626181747 DOT A5675 AT cygnus DOT com> <20000627004702 DOT A15783 AT cygnus DOT com>
	<m33dlzco28 DOT fsf AT MILHOUSE DOT cs DOT cornell DOT edu>
From: Paul Stodghill <stodghil AT CS DOT Cornell DOT EDU>
In-Reply-To: Paul Stodghill's message of "27 Jun 2000 08:21:03 -0400"
Date: 29 Jun 2000 14:43:48 -0400
Message-ID: <m3lmzo2uqj.fsf_-_@MILHOUSE.cs.cornell.edu>
Lines: 64
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

> 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?


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com