* John Reiser:
>>> Thinking aloud: does anyone ever use symbol overriding
for anything
>>> other than glibc?
>> Yes. It is particularly useful for "spear fishing" debugging of
lower-level
>> interfaces in large, complex multi-process applications.
> That only seems to need shallow interposition, though. In most cases, I
> doubt you are interested in API calls from the library self because
> those are probably unproblematic.
One actual case: why exp(600.0) ? Yes, the first use of overriding
was shallow and libm (part of glibc). But the caller was deep within
a scientific library, and the second overriding was not shallow at
all.
That's still unaffected. What I meant is that you can still alter calls
at library boundaries. Only purely internal calls are gone.
Thanks,
Florian