Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 Date: Tue, 30 May 2000 09:58:26 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Somewhat off-topic: Does cygwin net release gdb run "out of the box" for you? Message-ID: <20000530095826.C8894@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <20000530133429 DOT 6958 DOT qmail AT web114 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000530133429.6958.qmail@web114.yahoomail.com>; from earnie_boyd@yahoo.com on Tue, May 30, 2000 at 06:34:29AM -0700 On Tue, May 30, 2000 at 06:34:29AM -0700, Earnie Boyd wrote: >--- Chris Faylor wrote: >> 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. >> > >Hmm... I noticed this but I didn't install the gdb into a normal location. >After I downloaded the tarball and extracted, I tried running ./bin/gdb and the >program simply ended, no warnings, no errors and no screens. I moved gdb.exe >to /usr/bin and it brought up the windows, however, it still couldn't stat the >file on the tk side. Hmm. In a "normal" installation /bin == /usr/bin, so moving gdb.exe to /usr/bin should have either been a no-op, if you used cygwin tools, or it would have made gdb.exe unavailable if you used Windows tools. cgf