Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <08b201c20b33$0d4c7f70$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad.Scott@dsl.pipex.com>
To: <cygwin@cygwin.com>
References: <02fd01c20b12$49edbff0$0201a8c0@neeeeeee> <20020603163346.GB22575@redhat.com> <082e01c20b29$6bd04090$6132bc3e@BABEL> <20020603185243.GB25368@redhat.com>
Subject: Re: numerous bugs i've found in cygwin while developing XEmacs
Date: Mon, 3 Jun 2002 20:15:40 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

"Christopher Faylor" <cgf@redhat.com> wrote:
> On Mon, Jun 03, 2002 at 07:06:44PM +0100, Conrad Scott wrote:
> >I needed to download the (currently experimental) gdb 20020411-1 version
> >to be able to attach to processes, so there might be an easy fix for that
> >particular issue :-)
>
> gdb has been able to attach to a process for several years.

Well, I'm not going to re-install the previous version to check this, but I
recall that I had to upgrade to get something pretty major to work; like, if
it wasn't attaching to processes it was using core files --- something on
that scale. But maybe it was just a phase of the moon error (or, gulp, pilot
error).

// Conrad


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/