[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Does dropping objects really free memory?
From: |
Marcus G. Daniels |
Subject: |
Re: Does dropping objects really free memory? |
Date: |
20 Oct 1999 13:19:40 -0700 |
User-agent: |
Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.4 |
>>>>> "MD" == Marcus G Daniels <address@hidden> writes:
MD> You'll want to drop the selfConfig block...
Btw, in setLength: you use calloc to get memory for selfConfig. Then
in copy: you use alloc: for selfConfig. Since alloc: encodes some
information in start of the block it gets from malloc, you can't just
use "free (pointerFromAlloc)". Likewise, you can't use `free:' on the
result of a calloc.
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.
- Re: Does dropping objects really free memory?, (continued)
Re: Does dropping objects really free memory?, Marcus G. Daniels, 1999/10/19
Re: Does dropping objects really free memory?, famasce, 1999/10/20