From:	"Bryan Rosenburg"<rosnbrg AT watson DOT ibm DOT com>
Subject:	Re: GDB problem
9 Jul 1997 06:58:36 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<852564CF.00429AA7.00.cygnus.gnu-win32@watngi01.watson.ibm.com>
Mime-Version:	1.0
X-Lotus-FromDomain:	IBM RESEARCH
Original-To:	gnu-win32 AT cygnus DOT com
Original-cc:	noer AT cygnus DOT com, shebs AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

I wrote:
> On four of our Windows-95 machines, a simple "gdb -nw" followed
> by "quit" results in an "illegal operation" error but has no other ill
> effects.  But on the fifth machine, the same sequence consistently
results
> in gdb hanging in an unkillable state and consuming 90% or more of the
CPU.

The gdb hanging problem turned out to be of our own making.  On the problem
machine we had a "default application debugger" (not gdb) installed, but
the
debugger was misconfigured.  When gdb generated its illegal operation on
exit
(which it always does), the system went into a loop trying to invoke the
debugger executable which wasn't where it was supposed to be.  With no
default debugger installed, gdb's illegal operation on exit is benign.

With this problem solved, gdb in b18 has been quite stable and useful.

Bryan Rosenburg
rosnbrg AT watson DOT ibm DOT com


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -