This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/19317] [4.1 Regression] removing a temporary return value when we cannot
- From: "bernie at develer dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 May 2005 20:45:22 -0000
- Subject: [Bug c++/19317] [4.1 Regression] removing a temporary return value when we cannot
- References: <20050107191510.19317.mueller@kde.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bernie at develer dot com 2005-05-18 20:45 -------
(In reply to comment #36)
> (In reply to comment #35)
> > I'm still seeing the artsd miscompilation with
> > gcc 4.0.0 20050512 (Red Hat 4.0.0-5), which contains everything
> > from gcc-4_0-branch upto 13-05-2005 (circa).
>
> A backtrace showing a crash is not a very useful bug report, and probably has
> nothing to do with this bug report. It might not even be a gcc bug, as the
> konqueror failure was not. If you can track down the miscompilation, we'd
love to hear about it in a new bug report.
My backtrace looks suspiciously similar to the backtrace
reported in comment #14. My backtrace is from an
arts client, not from the artsd server, but they do
share lots of common code.
I've tried to debug the problem: something weird happens
in the destructor of a vector<string>, then GDB seems to
get confused by stack/registers corruption. It really
looks like a code generation bug to me.
Reducing a testcase isn't trivial, but I'll try.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19317