This is the mail archive of the
mailing list for the GCC project.
Re: FW: ostringstream: problems with str() function
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: FÖLDY Lajos <foldy at rmki dot kfki dot hu>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 24 Aug 2006 14:56:54 -0700
- Subject: Re: FW: ostringstream: problems with str() function
- References: <Pine.LNX.email@example.com>
On Thu, Aug 24, 2006 at 04:36:22PM +0200, Jordan, Laszlo (GE Healthcare) wrote:
> > I had a crash in our software, which occured randomly. The valgrind logs
> > and the stack trace pointed to a code snippet, which uses ostringstream
> > for data conversion....
> > The problem occured with gcc 3.4.2 and 3.4.4 compilers with -O2
> > optimization...
> > valgrind tool signs the following problems:
> > ==5443== Conditional jump or move depends on uninitialised value(s)
> > ==5443== at 0x11CD3445: std::string::string(std::string const&) (in
> > /usr/lib64/libstdc++.so.6.0.7)
On Thu, Aug 24, 2006 at 09:48:10PM +0200, FÖLDY Lajos wrote:
> probably a library version mismatch, libstdc++.so.6.0.7 belongs to GCC
Good catch. I guess that resolves the issue (and explains why others
have failed to duplicate it).