Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Mon, 29 May 2000 00:15:31 -0400
To:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Somewhat off-topic: Does cygwin net release gdb run "out of the box" for you?
Message-ID:	<20000529001531.A1468@cygnus.com>
Reply-To:	cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To:	cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.2i

I'm trying to track down the problems that people have been reporting
with gdb so I was starting from scratch with a net release.

I was surprised to find that gdb just returned to the prompt when I did
this.

I recognize the symptom and I know how to fix this but I wasn't having
this problem on my system until I "updated" to the net release.

So, I'm wondering if I screwed up the last gdb net release more than
a month ago and have been ignoring the pleas for help in the cygwin
mailing list.

The workaround for the problem is to set TCL_LIBRARY.  I wasn't doing
that though, so I must have been using a modified version of
cygtcl80.dll.

cgf

- Raw text -