From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-77090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 21364 invoked by alias); 28 Nov 2003 15:19:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 21226 invoked by uid 48); 28 Nov 2003 15:19:06 -0000
Date: Fri, 28 Nov 2003 15:19:00 -0000
From: "paolo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Message-ID: <20031128151902.13217.paolo@gcc.gnu.org>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug libstdc++/13217] New: basic_filebuf::underflow doesn't deal gracefully with read errors
X-Bugzilla-Reason: CC
X-SW-Source: 2003-11/txt/msg02496.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

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