[Ltrace-devel] Getting prototypes from debug information

[Luca Clementi]

On Wed, Apr 9, 2014 at 3:50 PM, Dima Kogan <lists at dima.secretsauce.net> wrote:
>
> Petr Machata <pmachata at redhat.com> writes:
>
> > Dima Kogan <lists at dima.secretsauce.net> writes:
> >
> >> Currently it appears that all function prototypes are read from the
> >> .conf files. Can these be read in from the debug information instead?
> >
> > They sure can.
> >
> >> ltrace already uses libdw, so I'm assuming either this is not possible,
> >> or it's on somebody's short-term todo list. Any thoughts about it?
> >
> > It uses it optionally for unwinding, yes.  It could use it optionally
> > for prototype retrieval as well.  This idea has crossed my mind in the
> > past, and I wouldn't oppose patches that extend ltrace into accepting
> > debuginfo if available.
>
> OK, I'll take a look. By the way, what was the issue with libunwind?
> Isn't unwinding the whole point of that library?
>

Few month ago Mark posted a patch to alternatively use elfutils to
unwind the stack (instead of libunwind).
They both do the same thing and share also a lot of code.

https://www.mail-archive.com/ltrace-devel@lists.alioth.debian.org/msg00731.html

Luca