From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: fork() + file descriptor bug in 1.7.27(0.271/5/3) 2013-12-09 11:54
Date: Fri, 17 Jan 2014 09:28:00 -0000 [thread overview]
Message-ID: <20140117092837.GI2831@calimero.vinschen.de> (raw)
In-Reply-To: <491859.27055.bm@smtp113.sbc.mail.ne1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
On Jan 16 23:53, tednolan@bellsouth.net wrote:
> In message <20140116085026.GA26205@calimero.vinschen.de>you write:
> >
> >Can you change your testcase another bit, please? Enable your
> >`ftell' printf, but rather than printing the result of ftell,
> >print the result of lseek:
> >
> > fprintf(stderr, "(%s) (%s) %d %ld\n", infile,
> > outfile, i, lseek(fileno(fp), 0, SEEK_CUR));
> >
> >I would be curious what happens on Solaris here.
> >
>
> OK,
>
> I took the original test case and made your lseek change. Here are
> the Solaris & FreeBSD results.
>
> Here is Solaris 9:
>
> =====================SOLARIS========================
> Script started on Thu Jan 16 23:47:20 2014
> solabel10% ./a.out < test_data
> (00.tif) (00.eps) 1 45
> Running 0
> child
> (01.tif) (01.eps) 2 15
> Running 1
> child
> (02.tif) (02.eps) 3 0
> Running 2
Thanks! That's exactly what happens on Cygwin as well.
I'm about to check in code to newlib which allows to choose between
Solaris/POSIX semantics to BSD/Linux semantics(*) at build time. Since
Linux is our role model, we're going to switch to BSD/Linux semantics
for the next Cygwin release as well.
Thanks,
Corinna
(*) More precise: BSD/Glibc semantics.
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-01-17 9:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:31 tednolan
2014-01-14 10:18 ` Corinna Vinschen
2014-01-14 15:54 ` Eric Blake
2014-01-14 16:15 ` tednolan
2014-01-15 4:53 ` Lord Laraby
2014-01-15 5:40 ` Lord Laraby
2014-01-15 7:46 ` Peter Rosin
2014-01-15 15:53 ` tednolan
2014-01-15 16:33 ` Corinna Vinschen
2014-01-16 5:08 ` tednolan
2014-01-16 8:50 ` Corinna Vinschen
2014-01-17 5:19 ` tednolan
2014-01-17 9:28 ` Corinna Vinschen [this message]
2014-01-17 20:13 ` Eric Blake
2014-01-17 20:11 ` Eric Blake
2014-01-17 20:38 ` Eric Blake
2014-01-17 21:02 ` tednolan
2014-01-17 22:12 ` Eric Blake
2014-01-17 23:25 ` Lord Laraby
2014-01-15 16:40 ` Tom Honermann
2014-01-15 16:50 ` Corinna Vinschen
2014-01-17 20:06 ` Eric Blake
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=20140117092837.GI2831@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).