public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>,
	 Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH] Add comments to explain when a stream is freed by, __libc_freeres().
Date: Tue, 26 May 2020 15:18:44 +0200	[thread overview]
Message-ID: <87mu5ueswb.fsf@igel.home> (raw)
In-Reply-To: <878sherg6h.fsf@oldenburg2.str.redhat.com> (Florian Weimer's message of "Tue, 26 May 2020 15:15:02 +0200")

On Mai 26 2020, Florian Weimer wrote:

> Most general allocations are also reachable.  They are linked from
> various free lists, after all.  I don't think that's a useful criterion.

There is no official API to iterate over all allocations.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2020-05-26 13:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 20:37 Carlos O'Donell
2020-05-25 15:30 ` Florian Weimer
2020-05-25 21:17   ` Carlos O'Donell
2020-05-26  7:53     ` Florian Weimer
2020-05-26  8:16       ` Andreas Schwab
2020-05-26  8:39         ` Florian Weimer
2020-05-26  8:53           ` Andreas Schwab
2020-05-26  9:31             ` Florian Weimer
2020-05-26  9:37               ` Andreas Schwab
2020-05-26 12:31                 ` Florian Weimer
2020-05-26 12:57                   ` Andreas Schwab
2020-05-26 13:15                     ` Florian Weimer
2020-05-26 13:18                       ` Andreas Schwab [this message]
2020-05-26 13:23                         ` Florian Weimer
2020-06-04 18:35       ` Carlos O'Donell

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=87mu5ueswb.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).