public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: aaronw@net.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8245: Crash in destructors on Solaris, no __cxa_atexit present
Date: Mon, 13 Jan 2003 00:51:00 -0000	[thread overview]
Message-ID: <20030113005100.7329.qmail@sources.redhat.com> (raw)

Synopsis: Crash in destructors on Solaris, no __cxa_atexit present

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Sun Jan 12 16:50:59 2003
State-Changed-Why:
    Can you provide a somewhat smaller testcase for this problem?
    Compiling (and installing) KDE is a somewhat too-large
    testcase to try to reproduce this problem. Please see the
    bug-reporting instructions on gcc.gnu.org to see what we
    would need.
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8245


             reply	other threads:[~2003-01-13  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13  0:51 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-02  0:07 giovannibajo
2002-10-16 14:46 aaronw

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=20030113005100.7329.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=aaronw@net.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).