some symbols of libc may be resolved by RTLD internal entities.

Hi,

It seems that some symbols in libc is resolved by libc entities
which is linked with RTLD to implement it.

% nm -D ld-elf.so.1
...
000158ec T mmap
0000c4fc W mprotect
0000c4dc W munmap
...

And running Flash9 with Symbol Versioning-aware Linux Plugin Wrapper
shows that mmap cannot be overrided. mmap is called with strange
argument.

4201 seamonkey-bin CALL mmap(0xffffffff,0x100000,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_FIXED|MAP_RENAME,0xffffffff,0,0,0x280875e4)
But sometimes munmap can be hooked.

Is this intended behavior that libc symbols in rtld is exported?
And are there any way to stop exporting it?


_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: File descriptor for shared mapping
    ... is mmap the only way a process can ... get a mapping to a file, ... Even if they do, mmapcalls inside libc could not be intercepted, as they ... If you want to intercept *really all* mappings, your only choice is to catch ...
    (comp.os.linux.development.apps)
  • Re: Malloc & sbrk
    ... *default* malloc implementation in libc (not libumem, etc.), does ... *not* use mmap for small blocks. ...
    (comp.unix.programmer)