Mail Archives: djgpp-workers/2003/03/18/13:51:48
Charles Sandmann wrote:
>
> > > It needs to be identical compatible, or it needs updated info
> > > documentation describing what's different. It also needs to compile
> > > into the library environment and work with the test programs, or
> > > they also need to be modified.
> >
> > That last is the hook that I can't/won't provide. I will be
> > providing my own test program to check the interface functioning.
>
> Is this because the code is incapable of doing these things, or
> you are just so opposed to the current interface you refuse to
> support it?
>
> I don't see a problem with a different test program as long as it
> tests library functions to display similar information.
'similar' is just fine.
It is a case of putting a limit on the things into which I will
burrow. There are many things I would like to learn and
investigate, but as I get older and approach dotage I realize that
I simply cannot do it all, and that I have to put limits on
things.
I gather the whole hook mechanism is new, so I see no problem with
using realloc entry/exit hooks, which require no assumptions
whatsoever. The documentation for realloc_hook that I got says,
in part, "called by free and malloc if and when realloc calls
them".
I am trying to implement mallinfo and mallocmap first, together
with the hooks. Next will be malloc_verify, and meanwhile
malloc_debug will just be setting an internal variable. I have
all the data structures already, the problem is getting hold of
the head of them, since each time sbrk returns an unexpected value
a new chain is started. I may be forced to change the basic
system slightly in order to record this.
--
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!
- Raw text -