Stephen Kell

It could also be useful in libsystrap for lazy instrumentation: make uninstrumented code "virtually executable" but turn off the X bit. On taking a trap, instrument a whole number of...

Following the fix of #47 we're part of the way there: we have a custom loader. It doesn't do very much, though. I'm debating whether we should abandon link-time instrumentation,...

Thanks Matt! Indeed I'll have to look into it... it's not clear whether the information in CTF is sufficient. But the allocation sites thing is probably not an issue. Currently...

I agree. Currently the -meta.c file gets its own gzipped log stored alongside it under /usr/lib/meta. It might make sense to follow that pattern everywhere, and use similar pretty-printing and...

I was hoping that the use of Docker would isolate the guest build environment from the vagaries of the host. Or do you mean you're using the Dockerfile as an...

Ah yes, OK. Thanks for this. Yes, there is a mess in libsystrap around raw syscalls and including the right headers for these. I might be wrong, but my tentative...

Agreed. There is a little bit of FreeBSD code in-tree already, mostly providing an equivalent for the use of Linux's /proc/self/maps. It is #ifdef'd quite nastily, when it really needs...

Perhaps another way to think of this: declare the code that realises an allocator, rather than the entry points. Then, when we see that code on the stack, we know...

Also, on the subject of observing the first cast (or the first write), it's possible that the default liballocs instrumentation should perhaps be instrumenting these -- witness Guillaume's approach to...

I think any solution solution has to arrange that the dlbind library is the first DSO in link order which is allowed to contain uniqtype definitions. This is already almost...