This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/12776] [3.4 Regression] Seg Fault when <iostream> included
- From: "mckelvey at maskull dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Oct 2003 01:46:34 -0000
- Subject: [Bug libstdc++/12776] [3.4 Regression] Seg Fault when <iostream> included
- References: <20031026025446.12776.mckelvey@maskull.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12776
------- Additional Comments From mckelvey at maskull dot com 2003-10-27 01:46 -------
Subject: Re: [3.4 Regression] Seg Fault when <iostream> included
On Sunday 26 October 2003 08:18 am, you wrote:
> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12776
>
>
>
> ------- Additional Comments From carlo at alinoe dot com 2003-10-26 16:18
> ------- Subject: Re: New: Seg Fault when <iostream> included
>
> On Sun, Oct 26, 2003 at 02:54:52AM -0000, mckelvey at maskull dot com wrote:
> > Reading symbols from /usr/local/lib/libstdc++.so.6...done.
>
> Is that the correct libstdc++?
> You should link with the one that comes with the compiler.
> Perhaps this is one from an old installation?
>
> Please explain if you compiled this compiler yourself,
> and if so, how you amde sure that the correct libstdc++ is
> being used.
>
Yes, I built it myself, and the date of the compiler matches the date of
libstdc++.so.6. The bug has been promoted to NEW, so I'm assuming that
someone else has confirmed it.