Re: symbol conventions

[Wolfram Gloger]

Hi,

> Much of the libc functionality is hidden behind stub symbols.  For
> example, there exists a weak (W) definition of write() which calls a public
> (T) definition of __write().  However, this isn't consistent between all
> sorts of calls.  Looking at the source, we've identified three general
> idioms for stubs in glibc:
> 
> Case A:  Both user code and libc code share the public interface.
> For example, the entry point to malloc() is public and is used both by users
> and by stdio.
> 
>                user code
>               |         \
>               V          V
>        (T) malloc() <-- stdio/libio
>               |
>               V
>          internal code

Note that malloc is weak in glibc:

% nm --dynamic /lib/libc-2.1.3.so |grep malloc
0004effc T __libc_malloc
000d6cdc V __malloc_hook
000d6cd4 V __malloc_initialize_hook
0004effc W malloc
...

Regards,
Wolfram.