| 1 |
On 17 Apr 2008 at 20:38, Ashish Shukla wrote: |
| 2 |
|
| 3 |
> Just to confirm, is LAZY loading means delay loading of all |
| 4 |
> dependencies (shared objects) unless they're required (i.e. function |
| 5 |
> present in one of the dependencies being invoked), right ? |
| 6 |
|
| 7 |
it's not lazy loading but lazy binding (of .plt/.got entries), that is, |
| 8 |
the .so modules are loaded as usual as required by DT_NEEDED entries. |
| 9 |
|
| 10 |
what differs is the time when undefined symbols are resolved. BIND_NOW |
| 11 |
enforces that resolution at .so load time so if there're any unresolved |
| 12 |
symbols (which may never be used in a given run or at all) in the given |
| 13 |
.so, ld.so will complain. normally an .so should have all dependent libs |
| 14 |
listed in DT_NEEDED (and not have unresolvable symbols at all) but the X |
| 15 |
module load code is a bit weird and bends these rules, hence the problems. |
| 16 |
|
| 17 |
-- |
| 18 |
gentoo-hardened@l.g.o mailing list |
Archives