public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/18524] Missing calloc error checking in __cxa_thread_atexit_impl
Date: Tue, 06 Oct 2015 10:58:00 -0000	[thread overview]
Message-ID: <bug-18524-131-cE68c6E0E1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18524-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18524

--- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Ondrej Bilka from comment #1)
> Do you have patch for that. Only course of action is return which causes
> memory leak as you don't call destructor later.

I think the interface cannot be salvaged.  The required space for bookkeeping
needs to be allocated in .tbss, or separately, at the time .tbss is allocated. 
I don't think anything in the standard permits leaks or exceptions in this
context.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-10-06 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 13:35 [Bug nptl/18524] New: " fweimer at redhat dot com
2015-07-12  7:23 ` [Bug nptl/18524] " neleai at seznam dot cz
2015-10-06 10:58 ` fweimer at redhat dot com [this message]
2015-10-06 19:21 ` carlos at redhat dot com
2020-09-09 19:57 ` tavianator at tavianator dot com
2021-07-28 10:40 ` siddhesh at sourceware dot org

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-18524-131-cE68c6E0E1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).