Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 16 Sep 2003 18:00:29 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: isatty bug
Message-ID: <20030916220029.GS23057@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT GSO DOT 4 DOT 56 DOT 0309161538160 DOT 685 AT eos>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.56.0309161538160.685@eos>
User-Agent: Mutt/1.4.1i

On Tue, Sep 16, 2003 at 03:53:07PM -0500, Brian Ford wrote:
>>(gdb) p fstat(fd1, &stat1)
>>Segmentation fault (core dumped)
>>
>>now, why does GDB crash?
>>
>Maybe because gdb actually calls fstat instead of fstat64 since it doesn't
>get the magic link time redirection?  No idea really.

The current version of gdb just can't call functions from the prompt.  I
just fixed this recently.  It was a gdb bug.  I'm having a hard time
regenerating gdb from cvs recently, otherwise, I'd have a new update
out.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/