public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	pme@gcc.gnu.org, stephenw@cryptocard.com
Subject: Re: libstdc++/9756: __verbose_terminate_handler enters infinite loop
Date: Fri, 28 Feb 2003 19:11:00 -0000	[thread overview]
Message-ID: <20030228191124.14309.qmail@sources.redhat.com> (raw)

Synopsis: __verbose_terminate_handler enters infinite loop

Responsible-Changed-From-To: unassigned->pme
Responsible-Changed-By: bkoz
Responsible-Changed-When: Fri Feb 28 19:11:24 2003
Responsible-Changed-Why:
    Phil, I assigned this to you for the time being, okay?
State-Changed-From-To: open->analyzed
State-Changed-By: bkoz
State-Changed-When: Fri Feb 28 19:11:24 2003
State-Changed-Why:
    
    Hmmm. I believe libgcc_so does have versioning support. Can somebody confirm this is really the problem?
    
    Stephen can you give more detail about this bit:
     I seems that the library libgcc_s.so.1 has been changed between 3.2 and the latest CVS source, but does not have versioning support.
    
    That's bad news, if true. Perhaps something like 'check-abi' is needed for libgcc_so? What's the change? Is it something as simple as just adding a new exported symbol?
    
    -benjamin

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


             reply	other threads:[~2003-02-28 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28 19:11 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-28 21:06 Stephen M. Webb
2003-02-20 19:36 Stephen M. Webb
2003-02-20 17:06 Stephen M. Webb
2003-02-20 17:06 Phil Edwards
2003-02-20 16:26 Phil Edwards
2003-02-20 16:06 Stephen M. Webb
2003-02-19 22:06 Phil Edwards
2003-02-19 16:06 stephenw

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=20030228191124.14309.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=pme@gcc.gnu.org \
    --cc=stephenw@cryptocard.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).