public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/13217] New: basic_filebuf::underflow doesn't deal gracefully with read errors Date: Fri, 28 Nov 2003 15:19:00 -0000 [thread overview] Message-ID: <20031128151902.13217.paolo@gcc.gnu.org> (raw) In the always_noconv case, if _M_file.xsgetn returns -1 the situations is pretty good, but the exception raised has a misleading what of "invalid byte sequence in file". In the general case, the read error condition is not dealt with properly and no meaningful exception is raised, everything can happen at run time... -- Summary: basic_filebuf::underflow doesn't deal gracefully with read errors Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libstdc++ AssignedTo: paolo at gcc dot gnu dot org ReportedBy: paolo at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: Any http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13217
next reply other threads:[~2003-11-28 15:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-28 15:19 paolo at gcc dot gnu dot org [this message] 2003-11-28 15:19 ` [Bug libstdc++/13217] " paolo at gcc dot gnu dot org 2003-12-10 20:05 ` cvs-commit at gcc dot gnu dot org 2003-12-10 20:06 ` paolo 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=20031128151902.13217.paolo@gcc.gnu.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: 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).