public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47694] [4.3/4.4/4.5/4.6 Regression] Fortran read from named pipe fails to read all available data
Date: Mon, 14 Feb 2011 15:33:00 -0000	[thread overview]
Message-ID: <bug-47694-4-A8OlxaDc3K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47694-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-02-14 15:13:44 UTC ---
If one enables fbuf debugging (FBUF_DEBUG in fbuf.c), one sees:

fbuf_read done: fbuf_debug pos: 0, act: 14, buf: ''LINE 1
LINE 2
''
Then the expected:
           1 LINE 1
is printed.


The next call to fbuf_read shows the correct buffer, which could directly be
used:

fbuf_read, len 1024: fbuf_debug pos: 0, act: 7, buf: ''LINE 2
''

But nevertheless, sread is invoked again:

fbuf_alloc len 1024, fbuf_debug pos: 0, act: 7, buf: ''LINE 2
''
reading 1017 bytes starting at 7 fbuf_debug pos: 0, act: 1024, buf: ''LINE 2
LINE 2


  parent reply	other threads:[~2011-02-14 15:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  7:34 [Bug fortran/47694] New: " David.Duffy at qimr dot edu.au
2011-02-11 14:42 ` [Bug fortran/47694] " burnus at gcc dot gnu.org
2011-02-11 20:12 ` jvdelisle at gcc dot gnu.org
2011-02-11 20:40 ` burnus at gcc dot gnu.org
2011-02-11 22:01 ` [Bug fortran/47694] [4.3/4.4/4.5/4.6 Regression] " burnus at gcc dot gnu.org
2011-02-14 14:55 ` burnus at gcc dot gnu.org
2011-02-14 15:33 ` burnus at gcc dot gnu.org [this message]
2011-02-14 21:32 ` burnus at gcc dot gnu.org
2011-02-14 22:08 ` burnus at gcc dot gnu.org
2011-02-15  1:24 ` jvdelisle at gcc dot gnu.org
2011-02-15  9:14 ` burnus at gcc dot gnu.org
2011-02-15  9:50 ` jb at gcc dot gnu.org
2011-02-17  1:13 ` jvdelisle at gcc dot gnu.org
2011-02-17 12:14 ` jb at gcc dot gnu.org
2011-02-17 13:16 ` jvdelisle at gcc dot gnu.org
2011-02-19  0:23 ` jvdelisle at gcc dot gnu.org
2011-02-22 19:59 ` jb at gcc dot gnu.org
2011-02-23  7:12 ` jb at gcc dot gnu.org
2011-02-23  7:53 ` jb at gcc dot gnu.org
2011-02-24 13:18 ` burnus at gcc dot gnu.org
2011-02-24 14:24 ` burnus at gcc dot gnu.org
2011-02-24 15:08 ` jb at gcc dot gnu.org
2011-02-24 15:23 ` jb at gcc dot gnu.org
2011-03-04 14:43 ` jvdelisle at gcc dot gnu.org
2011-03-05  0:06 ` jvdelisle at gcc dot gnu.org
2011-03-05  0:21 ` jvdelisle at gcc dot gnu.org
2011-03-05  9:54 ` burnus at gcc dot gnu.org
2011-03-05 15:40 ` jvdelisle at gcc dot gnu.org
2011-03-07  3:09 ` jvdelisle at gcc dot gnu.org
2011-03-07  3:16 ` jvdelisle at gcc dot gnu.org
2011-03-07  3:17 ` jvdelisle at gcc dot gnu.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=bug-47694-4-A8OlxaDc3K@http.gcc.gnu.org/bugzilla/ \
    --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).