public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/26123] Segmentation fault in constructor of std::ostream::sentry::sentry
Date: Mon, 06 Feb 2006 12:54:00 -0000	[thread overview]
Message-ID: <20060206125427.18753.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26123-12142@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pinskia at gcc dot gnu dot org  2006-02-06 12:54 -------
foo.cc has nothing to do with the problem here.  It all has to do with the
order of the execution of the initializers.

The following code is enough to reproduce the issue:
int mkCint();
const int cInt = mkCint();
#include <iostream>
int main()
{
    std::cout << cInt << std::endl;
}
int mkCint()
{
    std::cout << "mkCint()" << std::endl;
    return 2;
}


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26123


  parent reply	other threads:[~2006-02-06 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 12:44 [Bug libstdc++/26123] New: " broeni at osb-systems dot com
2006-02-06 12:52 ` [Bug libstdc++/26123] " pinskia at gcc dot gnu dot org
2006-02-06 12:54 ` pinskia at gcc dot gnu dot org [this message]
2006-02-06 12:56 ` [Bug libstdc++/26123] [3.4/4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-02-06 13:10 ` pcarlini at suse dot de
2006-02-06 13:13 ` [Bug libstdc++/26123] [3.4/4.0 " pinskia at gcc dot gnu dot org
2006-02-06 13:16 ` pcarlini at suse dot de
2006-02-06 15:07 ` rguenth at gcc dot gnu dot org
2006-02-06 19:28 ` broeni at osb-systems dot com
2006-02-07 12:52 ` broeni at osb-systems dot com
2006-02-07 13:19 ` broeni at osb-systems dot com
2006-02-07 13:59 ` pcarlini at suse dot de
2006-04-22 19:54 ` pcarlini at suse dot de

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060206125427.18753.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).