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

When compiled with:
  g++-4.0 -g -Wall   -c -o try.o try.cc
  g++-4.0 -g -Wall   -c -o foo.o foo.cc
  g++-4.0 -g -Wall -o try try.o foo.o
the program below creates a segmentation fault.

UNIX> gdb ./try
(gdb) r
Starting program: /data/home/osb/temp/clcpp/try 

Program received signal SIGSEGV, Segmentation fault.
0xb7f83de5 in std::ostream::sentry::sentry () from /usr/lib/libstdc++.so.6

try.h
=====
#ifndef TRY_H
#define TRY_H

int mkCint();
const int cInt = mkCint();

#endif

try.cc
======
#include "try.h"
#include <iostream>

int main()
{
    std::cout << cInt << std::endl;
}

int mkCint()
{
    std::cout << "mkCint()" << std::endl;
    return 2;
}

foo.cc
======
#include "try.h"

Notes
If stdout instead of std::cout is used OR
if compiled with g++-3.3 the program runs as expected:
UNIX> ./try
mkCint()
mkCint()
2
UNIX>


-- 
           Summary: Segmentation fault in constructor of
                    std::ostream::sentry::sentry
           Product: gcc
           Version: 4.0.3
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: broeni at osb-systems dot com
 GCC build triplet: i486-pc-linux-gnu
  GCC host triplet: i486-pc-linux-gnu
GCC target triplet: i486-pc-linux-gnu


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


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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 12:44 broeni at osb-systems dot com [this message]
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
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=bug-26123-12142@http.gcc.gnu.org/bugzilla/ \
    --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).