From: Roland McGrath <roland@redhat.com>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: [mark@codesourcery.com: libc/4926: __cxa_finalize mishandles a NULL dso parameter]
Date: Thu, 05 Dec 2002 13:14:00 -0000 [thread overview]
Message-ID: <200212052114.gB5LEYh20830@magilla.sf.frob.com> (raw)
[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 250 bytes --]
If that reference is indeed the spec, then this change needs to be made.
But before I put it in I am wondering whether there might be any gotchas,
i.e. existing binaries that depend on the erroneous behavior. If so,
we should do some versioning.
[-- Attachment #2: forwarded message --]
[-- Type: message/rfc822, Size: 1800 bytes --]
From: mark@codesourcery.com
To: libc-gnats@gnu.org, gnats-admin@gnu.org
Subject: libc/4926: __cxa_finalize mishandles a NULL dso parameter
Date: Thu, 05 Dec 2002 16:04:31 -0500
Message-ID: <E18K3Ad-00078g-00@fencepost.gnu.org>
>Number: 4926
>Category: libc
>Synopsis: __cxa_finalize mishandles a NULL dso parameter
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: libc-gnats
>State: open
>Quarter:
>Keywords:
>Class: sw-bug
>Submitter-Id: gnatsweb
>Arrival-Date: Thu Dec 05 16:04:31 -0500 2002
>Cases:
>Originator: mark@codesourcery.com
>Release:
>Organization:
>Environment:
>Description:
When __cxa_finalize is called with a NULL DSO handle, it
should run *all* cleanups; instead it runs none of the
cleanups.
See:
htttp://www.codesourcery.com/cxx-abi/abi.html
for the specification of this function.
>How-To-Repeat:
>Fix:
Unknown
>Unformatted:
next reply other threads:[~2002-12-05 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 13:14 Roland McGrath [this message]
2002-12-05 13:23 ` Ulrich Drepper
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=200212052114.gB5LEYh20830@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=libc-hacker@sources.redhat.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).