public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: peturr02@ru.is To: gcc-gnats@gcc.gnu.org Subject: libstdc++/9964: filebuf::close() sometimes fails to close file. Date: Wed, 05 Mar 2003 12:56:00 -0000 [thread overview] Message-ID: <20030305124917.25796.qmail@sources.redhat.com> (raw) >Number: 9964 >Category: libstdc++ >Synopsis: filebuf::close() sometimes fails to close file. >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Mar 05 12:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: peturr02@ru.is >Release: gcc-3.2.1 >Organization: >Environment: Red Hat Linux 8.0 >Description: It seems that if the call to _M_really_overflow in filebuf::close() fails, then close() doesn't close the file and doesn't delete the buffer. >How-To-Repeat: See attachment. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="closebug.cc" Content-Disposition: inline; filename="closebug.cc" #include <unistd.h> #include <signal.h> #include <fcntl.h> #include <sys/types.h> #include <sys/stat.h> #include <fstream> #undef NDEBUG #include <cassert> int main() { using namespace std; signal(SIGPIPE, SIG_IGN); unlink("xxx"); if (0 != mkfifo("xxx", S_IRWXU)) { assert(false); } int fval = fork(); if (fval == -1) { unlink("xxx"); assert(false); } else if (fval == 0) { filebuf fbin; fbin.open("xxx", ios_base::in); sleep(1); fbin.close(); exit(0); } filebuf fb; fb.open("xxx", ios_base::out | ios_base::trunc); assert(fb.is_open()); sleep(2); fb.sputc('a'); filebuf* p = fb.close(); assert(!p); assert(!fb.is_open()); return 0; }
next reply other threads:[~2003-03-05 12:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-05 12:56 peturr02 [this message] 2003-03-22 9:21 paolo
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=20030305124917.25796.qmail@sources.redhat.com \ --to=peturr02@ru.is \ --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: linkBe 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).