Re: (interposers): How to workaround the "strong symbols" problem?

Am 18.01.25 um 01:42 schrieb Kenny McCormack:

Right.  It seems to boil down to:
      You can't interpose a syscall.
 I.e., so if a library function calls the syscall directly (rather than
going through the Glibc wrapper), you can't interpose it.  This is, of
course, as it should be.

Hmm, it may be related to optimizations. Assuming the openat call is inlined in another compilation unit there is no option to change this at link time.
Marcel