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
X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs
Date: Tue, 16 Sep 2003 15:53:07 -0500 (CDT)
From: Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: cygwin AT cygwin DOT com
Subject: Re: isatty bug
Message-ID: <Pine.GSO.4.56.0309161538160.685@eos>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Sam Steingold wrote:

> it turned out that I needed to recompile the obj file that defined my
> same_tty_p() - of course.  how silly of me!  [now, I think I was told
> that everything was binary backwards compatible; I guess I was confused]
> now that I did it -- my scratch.c works just like your stest.c.
> good.
>
Executables (and DLLs) are binary backwards compatible.  Static libs
and objects are not.  The 64 bit translation happens at link time.

> (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.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/