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
Message-ID: <20000530140515.28940.qmail@web120.yahoomail.com>
Date: Tue, 30 May 2000 07:05:15 -0700 (PDT)
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: earnie_boyd AT yahoo DOT com
Subject: Re: Somewhat off-topic:  Does cygwin net release gdb run "out of the box" for you?
To: cygwin-developers AT sourceware DOT cygnus DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Chris Faylor <cgf AT cygnus DOT com> wrote:
> On Tue, May 30, 2000 at 06:34:29AM -0700, Earnie Boyd wrote:
> >--- Chris Faylor <cgf AT cygnus DOT com> 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.

Yep, /usr/bin == /bin.


=====
---
   Earnie Boyd: <mailto:earnie_boyd AT yahoo DOT com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/