|
From: Nicholas N. <nj...@ca...> - 2003-03-24 13:19:32
|
On Mon, 24 Mar 2003, Josef Weidendorfer wrote: > > Hmm, one problem is that it requires glibc to not be stripped, since > > spotting function entries relies on symbol information being present. > > I'm not sure whether this is likely or not. > > Symbol information for exported symbols in shared libraries can't be stripped, > as the runtime linker has to know about it. This isn't debug information, and > thus no problem. Ah, good, so no problem there. > I still think that wrapping malloc() is a skin issue, and the core only should > provide convenience functions for doing this in a simply way... I agree. N |