[Ltrace-devel] [PATCH 2/2] configuration: added 'include' statement

[Petr Machata]

Enrico Scholz <enrico.scholz at sigma-chemnitz.de> writes:

> Petr Machata <pmachata at redhat.com> writes:
>
>> When a library is mapped in, ltrace looks for <soname>.conf
>
> oh, I was not aware of this feature (and do not find any documentation
> about it).  I guess, it is a very recent feature not available e.g. in

I should fix that.  I thought there was something in the man page about
it, but there isn't.

> Fedora 19 yet, isn't it?

Yeah, Fedora ships 0.7.2 with some patches piled on top.  This
functionality is on master.

> When it is working as you describe, there is not very much need for
> including other files as done by my patch.  Perhaps to include common
> definitions for different so-versions of a library.  But I will have to

Yes, I imagine different libc's might want to share some base
definitions (and add more library-specific stuff on top), and other
libraries might want to load e.g. just libc typedefs (if they use them
in interfaces themselves.  Exposing typedefs like FILE should be fairly
useful).  Possibly libX.so.<Y> might want to import libX.so.<Y-1> for
the shared stuff, and override the changed API's.

Some sort of wild-carding might still be useful--e.g. if libX.so.5.conf
doesn't exist, ltrace might look for libX.so.conf--perhaps the full DSO
version doesn't matter for libX.

> see this for real world use cases before I can say whether this is
> really needed.
>
>> in /etc/ltrace/
>
> It does not really matter, but global so-name definition files (e.g. shipped
> by <lib>-devel packages) are no configuration files imo and should be placed
> e.g. into /usr/share/ltrace or so.

That's a good point.  Another option might be /usr/lib/ltrace (they are
library files, after all, and /usr/lib is where e.g. RPM puts its macro
stuff).

Thanks,
PM