I don't know, if this is a possible way to go, nor how portable the
malloc code really is - anyway I did hack together parrot with malloc.c
from http://gee.cs.oswego.edu/dl/html/malloc.html.
s also http://www.cs.utexas.edu/users/oops/papers.html.
The whole resource.c is replaced by calls to
The whole resource.c is replaced by calls to calloc/realloc (res.c),
add_free_buffer does free().
I think that's the problem right there. What exactly are you changing
to use this new calloc/malloc implementation? One approach is to modify
memory.c to use the new versions, although since
Mike Lambert wrote:
The whole resource.c is replaced by calls to calloc/realloc (res.c),
add_free_buffer does free().
I think that's the problem right there. What exactly are you changing
to use this new calloc/malloc implementation? One approach is to modify
memory.c to use the new
