[Mesa-dev] RFC: Memory allocation on Mesa
timur.kristof at gmail.com
Tue May 12 09:00:52 UTC 2020
On Tue, 2020-05-12 at 08:51 +0000, Tamminen, Eero T wrote:
> On Tue, 2020-05-12 at 10:36 +0200, Timur Kristóf wrote:
> > On Mon, 2020-05-11 at 20:19 +0000, Tamminen, Eero T wrote:
> > > I've done a lot of resource usage analysis at former job, but
> > > I've
> > > never had needed anything like that. malloc etc all reside in a
> > > separate shared library from Mesa, so calls to them always cross
> > > dynamic library boundary and therefore all of them can be caught
> > > with
> > > the dynamic linker features (LD_PRELOAD, LD_AUDIT...).
> > I think he meant something like GCC's --wrap option, and wasn't
> > talking
> > about the dynamic linker.
> Using it requires relinking the SW to use, so I would use it only on
> some embedded platform which dynamic linker doesn't support better
> interception methods.
Yes, I agree that the dynamic linker is probably the best way to deal
with this kind of problem.
> (Note: "--wrap" isn't GCC options, but one for binutils ld.)
Indeed. Thanks for the correction.
More information about the mesa-dev