public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/20806] [3.4/4.0/4.1 Regression] basic_filebuf::xsgetn()  fails with text mode and DOS line endings and large buffers
Date: Thu, 07 Apr 2005 09:14:00 -0000	[thread overview]
Message-ID: <20050407091433.9306.qmail@sourceware.org> (raw)
In-Reply-To: <20050407083148.20806.dannysmith@users.sourceforge.net>


------- Additional Comments From pcarlini at suse dot de  2005-04-07 09:14 -------
> The problem is that the native read translates the input \r\n to
> \n,  returning the number of chars written,

This is a very fundamental assumption to break, which is likely to cause much
more problems elsewhere, maybe only latent now. The correct solution cannot
be just working around it in this function, instead something like using
unconditionally binary mode on mingw + libstdc++-v3. Ideas?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20806


  parent reply	other threads:[~2005-04-07  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07  8:31 [Bug libstdc++/20806] New: basic_filebuf::xsgetn() fails with text mode and dannysmith at users dot sourceforge dot net
2005-04-07  8:36 ` [Bug libstdc++/20806] basic_filebuf::xsgetn() fails with text mode and DOS line endings and large buffers dannysmith at users dot sourceforge dot net
2005-04-07  8:44 ` [Bug libstdc++/20806] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-04-07  9:14 ` pcarlini at suse dot de
2005-04-07  9:14 ` pcarlini at suse dot de [this message]
2005-04-07 10:25 ` pcarlini at suse dot de
2005-04-07 10:36 ` pcarlini at suse dot de
2005-04-07 13:03 ` pcarlini at suse dot de
2005-04-08 17:32 ` cvs-commit at gcc dot gnu dot org
2005-04-08 17:35 ` cvs-commit at gcc dot gnu dot org
2005-04-09  0:32 ` pcarlini at suse dot de
2005-04-21  5:05 ` mmitchel at gcc dot gnu dot org
2005-04-24 22:45 ` pcarlini at suse dot de
2005-04-25  0:32 ` pinskia at gcc dot gnu dot org

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=20050407091433.9306.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).