From: DJ Delorie <dj@redhat.com>
To: Eric Wong <e@80x24.org>
Cc: libc-alpha@sourceware.org
Subject: Re: status of dj/malloc branch?
Date: Mon, 08 Apr 2024 14:37:59 -0400 [thread overview]
Message-ID: <xnwmp74s54.fsf@greed.delorie.com> (raw)
In-Reply-To: <20240406220206.M748482@dcvr> (message from Eric Wong on Sat, 6 Apr 2024 22:02:06 +0000)
Eric Wong <e@80x24.org> writes:
> I started doing my own tracing[1] in mwrap-perl[2] and it's
> crazy expensive (I/O and storage) to trace all the allocations
Yeah, we ran into that problem too. 64-bit pointers plus many-argument
functions like realloc results in a HUGE log file. Like, terabytes in
one case.
prev parent reply other threads:[~2024-04-08 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 19:19 Eric Wong
2024-04-01 20:59 ` DJ Delorie
2024-04-06 22:02 ` Eric Wong
2024-04-08 18:37 ` DJ Delorie [this message]
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=xnwmp74s54.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=e@80x24.org \
--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).