public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: papadopo@shfj.cea.REMOVE.fr
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/8504: ios::app + pipes
Date: Fri, 08 Nov 2002 06:26:00 -0000	[thread overview]
Message-ID: <20021108141734.20177.qmail@sources.redhat.com> (raw)


>Number:         8504
>Category:       libstdc++
>Synopsis:       ios::app + pipes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 08 06:26:10 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     papadopo@shfj.cea.REMOVE.fr
>Release:        gcc-3.2
>Organization:
>Environment:
Solaris 8 7/01 + gcc-3.2
IRIX 6.5.13 + gcc-3.0.2
>Description:
fstream::open() with ios::app flag fails on pipes for gcc 3.0 and better.

This used to work fine with gcc 2.95.3.
>How-To-Repeat:
To reproduce:
- build the attached openapp.cc source file
- create a pipe named /tmp/pipe - use "mkfifo /tmp/pipe"
- run the program, it will attempt to open /tmp/pipe with
  fstream::open() and ios::app flag
- read the pipe from a shell to unblock - "cat /tmp/pipe"
- fstream::open() will fail with error "Illegal seek"
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="openapp.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="openapp.cc"

I2luY2x1ZGUgPGlvc3RyZWFtPgojaW5jbHVkZSA8ZnN0cmVhbT4KI2luY2x1ZGUgPGNzdHJpbmc+
CiNpbmNsdWRlIDxjZXJybm8+Cgp1c2luZyBuYW1lc3BhY2Ugc3RkOwoKaW50IG1haW4oKSB7CiAg
b2ZzdHJlYW0gcGlwZTsKICBwaXBlLm9wZW4oICIvdG1wL3BpcGUiLCBpb3M6Om91dHxpb3M6OmFw
cCApOwogIGlmKCAhcGlwZSApCiAgICBjZXJyIDw8ICJjb3VsZCBub3Qgb3BlbiBwaXBlICgiIDw8
IGVycm5vIDw8ICIsICIgPDwgc3RyZXJyb3IoZXJybm8pIDw8ICIpIiA8PCBlbmRsOwp9Cg==


             reply	other threads:[~2002-11-08 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08  6:26 papadopo [this message]
2002-11-22  9:23 paolo
2002-11-22 15:12 paolo
2003-02-03 13:05 paolo
2003-04-22 12:36 Dimitri Papadopoulos-Orfanos

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=20021108141734.20177.qmail@sources.redhat.com \
    --to=papadopo@shfj.cea.remove.fr \
    --cc=gcc-gnats@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).