public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Ford <ford@vss.fsi.com>
To: cygwin@cygwin.com
Subject: Re: isatty bug
Date: Tue, 16 Sep 2003 21:01:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0309161538160.685@eos> (raw)

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/

             reply	other threads:[~2003-09-16 20:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16 21:01 Brian Ford [this message]
2003-09-16 22:05 ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2003-09-16 19:34 Brian Ford
2003-09-16 20:28 ` Sam Steingold
2003-09-16 19:01 Brian Ford
2003-09-16 19:02 ` Sam Steingold
2003-09-15 21:19 Sam Steingold
2003-09-16 10:13 ` Corinna Vinschen
2003-09-16 15:01   ` Sam Steingold
2003-09-16 17:22     ` Christopher Faylor
2003-09-16 17:30       ` Sam Steingold
2003-09-16 17:37         ` Igor Pechtchanski
2003-09-16 18:23           ` Sam Steingold
2003-09-16 18:36             ` Igor Pechtchanski
2003-09-16 19:37             ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.56.0309161538160.685@eos \
    --to=ford@vss.fsi.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).