Stephen Kell

Back to the 'undefined weak' situation: instead of testing at every use, we could lightly hack the binary so that the dummy weaks *are* defined, locally, and what we have...

Perhaps one way to go is to bundle the stubs into our ld.so? Hmm. This is a can of worms. The thinking was that allocsld.so can be a library on...

(It's a can of worms because normally allocsld.so is not involved in linking. It is a chain loader only. This way, it would be filling both that role and the...

Recall: we want to support the "instrumentation disabled" case. That's why we don't just have allocscc do `-lallocs_preload` and then (at init time) check we're loaded in preload position.

I've a feeling IFUNCs are the answer. They're exactly answering the use case: choose a relocation target based on run-time information. We use the 'real' version if liballocs is in...

The most obvious reentrancy I see is bitmap malloc -> mmap -> malloc of a mapping_sequence. But his would work fine, because the mapping_sequence is O(nbigallocs). Again this is a...

Another one: - why make_precise wasn't the right interface, and how to do it better

More - why 'typedefs as aliases' isn't quite right, but is fixable - why 'global-symbol uniqueness' isn't quite right, for aliased uniqtypes

- why 'allocation hierarchy' isn't quite accurate (mmaps are a patchwork) but seems to be recoverable

- 'there is no static' / the dynamic linker as an allocator (arguably covered in 2015 paper, but good to go into)