From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cs.psu.edu
Subject: [9fans] questions about trump and leak
Date: Tue, 15 Apr 2003 23:05:36 +0200 [thread overview]
Message-ID: <200304152105.h3FL5a404419@zamenhof.cs.utwente.nl> (raw)
Triggered by Russ' mention of trump I tried to have a look
at memory usage/leaks of a simple file server I'm playing
with ('working on').
Trump seems to indicate a free for each malloc I'm concerned about
(assuming I'm interpreting its output correctly).
Trump also gives some lines starting with ``0x00000000 free'' ;
do they mean that free gets passed a null pointer? Or?
Leak -b produces an image containing a red part.
However, leak -s gives me nothing (immediately a prompt).
This confuses me; what am I missing?
I updated yesterday evening, and just some minutes ago
made /sys/src/libc/port/pool.acid (leak complained it to be missing)
Thanks,
Axel.
next reply other threads:[~2003-04-15 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 21:05 Axel Belinfante [this message]
2003-04-15 21:20 ` rsc
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=200304152105.h3FL5a404419@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cs.psu.edu \
/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 NNTP newsgroup(s).