Mail Archives: djgpp-workers/2002/10/21/01:44:52
Charles Sandmann wrote:
>
> > Glad someone is looking at it.
>
> We have a few problems...
>
> The code is significantly different from the current documentation and
> user interfaces in CVS/V2.04.
It is all brand new, with the exception of the structure of the
free list header. Unless somebody did it before, which is far
from impossible. I have tried NOT to be in the least tricky.
>
> The following external interfaces are missing:
> mallinfo
> malloc_debug
> malloc_verify
> mallocmap
> __libc_malloc_hook
> __libc_malloc_fail_hook
> __libc_free_hook
> __libc_free_null_hook
> __libc_realloc_hook
> __malloc_get_freelist
> __malloc_get_slop
> __malloc_get_bytes_in_use
> __malloc_get_chunks_in_use
> __malloc_get_sbrked
>
> These will need to be added, or alternate debugging routines written and
> documented. It appears retrofitting CBF's code with the above routines
> would be the right thing to do (but is fairly substantial work).
I made provisions for getting at the internal structure, and used
an example of it in the dumps from the testing code. If you will
give me the details of what those interfaces have to do I will see
(no promises) how they can be generated. The point to me is that
any such interfaces are done through header files, and leave the
malloc code itself free to do what it needs.
>
> There is also the question of stress testing the code. The easiest
> thing to do would be to fix the bare minimum naming to be libc compatible,
> dump it into a copy of libc.a, and try building the entire toolchain
> twice to see if all goes well. This would need a volunteer ...
I beat on it quite heavily, IMO. However I am not the one to do
that, as I have built-in opinions :-)
--
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 -