DragonFly BSD
DragonFly kernel List (threaded) for 2003-09
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Prebinding for DragonFly/FreeBSD-4

From: "Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>
Date: Sun, 14 Sep 2003 19:26:55 +0200

Lately Matthew N. Dodd told:

> Prebinding on a per executable basis rather than a per "object" (ELF
> executable or library) means that when you go to prebind KDE (for
> example) you run /var out of diskspace :/

Yes, that might be true. How about this approach:
(doesn't cope with cyclic ``needs'' yet)

- assign every .so a base address so that no collisions happen for every
  binary considered

Then, for every binary:
- start with resolving the last object (often libc), as if only this
  object was loaded
- proceed to the next object (might be another .so or the binary)
- there again, resolve stuff. if this changes resolved data in
  objects resolved before (global references...), save this data too,
  like deltas to the data of the object before.
- loop

This means: Every object has the data assigned which it ultimatively
requests. If globals etc exists they will overridden by the next object
which requested previous object.

On load, just run the same way. First, load data of the last object
(i.e. libc), then running the object list back to the binary, load data.
Globals that get resolved another way than without object X will be
overwriten by the patchup data for object X.

Uhg, I hope I made myself (at least partly) clear enough to follow.


/"\   http://corecode.ath.cx/#donate
\ /
 \     ASCII Ribbon Campaign
/ \  Against HTML Mail and News

Attachment: pgp00015.pgp
Description: PGP signature

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]