public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: キャロウ マーク <github@callow.im>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: Pipes truncating data in cygwin from main and cygwin-3_4-branch
Date: Tue, 15 Aug 2023 19:01:39 +0900	[thread overview]
Message-ID: <711F7C15-6A2C-47B2-B8FF-A02FB703A808@callow.im> (raw)
In-Reply-To: <FCF9C3F3-7ED6-406A-8420-05379E4C5875@callow.im>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]



> On Aug 15, 2023, at 18:09, キャロウ マーク <github@callow.im> wrote:
> 
> ...
> 
> I will put some tracing in `test-pipe.c++` to see whether it is currently buffering or not.

Indeed the seekg is returning success so my code uses the path where it is expected to work. If I force buffering, the test passes.

I tried the same tests in PowerShell instead of Git for Windows Bash. There too seekg() reports success.  If I force buffering tellg() after isp->seekg(0, ios_base::end) reports 171,926 bytes vs a file size of 170,512 which is strange. Without buffering tellg() reports 8192 bytes. Basically the same behaviour as with G4W bash except there tellg() reports 170,512 bytes and 126,976 bytes respectively.

> 
> We’ve only tested non-Cygwin consumers. When the author of the above GitHub issue comment was testing on Cygwin he compiled the consumer with mingw-w64 g++.
> 

If Cygwin consumers also see this changed seekg behaviour then they will have problems too.

Regards

    -Mark


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 528 bytes --]

      parent reply	other threads:[~2023-08-15 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13B0370E-B61A-44B9-A885-5FF1B8F4AC5F@callow.im>
2023-08-15  0:30 ` Takashi Yano
     [not found]   ` <CCC360AD-21B1-40E4-8B6B-FCFAF5612939@callow.im>
2023-08-15  6:42     ` Takashi Yano
     [not found]       ` <FCF9C3F3-7ED6-406A-8420-05379E4C5875@callow.im>
2023-08-15  9:45         ` Takashi Yano
2023-08-15 10:01         ` キャロウ マーク [this message]

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=711F7C15-6A2C-47B2-B8FF-A02FB703A808@callow.im \
    --to=github@callow.im \
    --cc=cygwin@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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).