This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: dec-2001 libstdc++ outstanding
- From: Paolo Carlini <pcarlini at unitus dot it>
- To: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Tue, 08 Jan 2002 10:07:04 +0100
- Subject: Re: dec-2001 libstdc++ outstanding
- References: <200201080740.g087e5400108@latour.rsch.comm.mot.com>
Loren James Rittle wrote:
>Both of these tests fail due to a variation of this straightforward
>construct:
>
>float x;
>std::istringstream iss([...]);
>iss >> x;
>VERIFY( iss.good() );
>
>Impossible to debug with gdb 4.18 on i386. Flow control very hard to
>follow with gdb 4.18 on alpha. Here is what I learned on alpha:
>std::istringstream::operation>>() fails since _M_streambuf_state was 4
>(_S_failbit). I have no idea how that is possible, but that is what I
>saw. Any clues from any of the above information? before I attempt to
>build mainline gdb in those environments.
>
Hi Loren,
Personally, I believe that in these days a CVS gdb is *really* needed in
order to effectively debug C++ code...
Alternatively, have you tried debugging
libstdc++-v3.0.95-gcc-3.0.3.tar.gz plugged in gcc3.0.3 ?
Cheers,
Paolo.