This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
suzuki wrote: > Hi, > The problem occurs when a library (say libA) is mapped (by glibc) in the > space between two loaded segments of an already mapped library ( we have > seen this library is most of the time ld-linux.so). There are only two objects which have that problem: ld.so and the application binary itself. The problem is that kernel which does not fill the gap when loading ld.so. I've complained about this many times but nothing happens. Your proposed change does not address the fact that other code could also depend on the address space range being used for one purpose. It's only dladdr which is changed. An alternative fix would be to fill in the gaps in ld.so after startup. This means two extra syscalls for all processes and only for the odd chance that somebody requests addresses. I have to think about it. -- â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |