public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rbsmithz@prodigy.net
To: libstdc++-gnats@sourceware.cygnus.com
Subject: libstdc++/1851: seg fault in global basic_string construction
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <20000129230620.30181.qmail@sourceware.cygnus.com> (raw)

>Number:         1851
>Category:       libstdc++
>Synopsis:       seg fault in global basic_string construction
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    ncm
>State:          feedback
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 03 09:26:03 PST 2001
>Closed-Date:    
>Last-Modified:  Tue Mar 21 00:37:00 PST 2000
>Originator:     Randall B. Smith
>Release:        libstdc++ 2.95.2-3
>Organization:
>Environment:
RedHat 6.1, gcc-c++ 2.95.2, libstdc++-3-libc6.1-2-2.10.0.so
>Description:
A segmentation fault occurs during global object construction
of basic_string objects. This was traced to the std/bastring.h
file which #included the std/bastring.cc file.
>How-To-Repeat:
This problem is quite intermittant at compile/link time.
Changes in unrelated areas of my code would may the
problem go away or reappear, e.g., just commenting a
statement or changing the length of a char * constant.
I can provide code if necessary, but it seems odd that
bastring.h includes bastring.cc, so I'll assume this is
an oversight.
>Fix:
Comment-out or remove line at the bottom of
/usr/include/g++-3/std/bastring.h:

//#include <std/bastring.cc>
>Release-Note:

>Audit-Trail:

Formerly PR libstdc++/29

Responsible-Changed-From-To: unassigned->ncm
Responsible-Changed-By: bkoz
Responsible-Changed-When: Tue Mar 21 00:27:20 2000
Responsible-Changed-Why:
    strings
State-Changed-From-To: open->feedback
State-Changed-By: bkoz
State-Changed-When: Tue Mar 21 00:27:20 2000
State-Changed-Why:
    This bug tracking database is for the libstdc++-v3 project: you are using libstdc++-v2. If you'd like to use libstdc++-v3, please see
    
    sourceware.cygnus.com/libstdc++
    
    thanks,
    benjamin

From: bkoz@cygnus.com
To: libstdc++-gnats@sourceware.cygnus.com, ncm@zembu.com,
  nobody@sourceware.cygnus.com, rbsmithz@prodigy.net
Cc:  
Subject: Re: libstdc++/29
Date: 21 Mar 2000 08:27:20 -0000

 Synopsis: seg fault in global basic_string construction
 
 Responsible-Changed-From-To: unassigned->ncm
 Responsible-Changed-By: bkoz
 Responsible-Changed-When: Tue Mar 21 00:27:20 2000
 Responsible-Changed-Why:
     strings
 State-Changed-From-To: open->feedback
 State-Changed-By: bkoz
 State-Changed-When: Tue Mar 21 00:27:20 2000
 State-Changed-Why:
     This bug tracking database is for the libstdc++-v3 project: you are using libstdc++-v2. If you'd like to use libstdc++-v3, please see
     
     sourceware.cygnus.com/libstdc++
     
     thanks,
     benjamin
 
 http://sourceware.cygnus.com/cgi-bin/gnatsweb.pl?cmd=view&pr=29&database=libstdc++
>Unformatted:



             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01  0:00 rbsmithz [this message]
2001-06-09 23:53 bkoz

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=20000129230620.30181.qmail@sourceware.cygnus.com \
    --to=rbsmithz@prodigy.net \
    --cc=libstdc++-gnats@sourceware.cygnus.com \
    /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).