ltrace

ltrace

[Petr Machata]

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Hi,

I committed first stab on ltrace for frysk, dubbed fltrace.  The output
is very rudimentary, but should at least print out library function
called from the executable itself.

fltrace is only known to work on i386 for non-PIE ELF binaries, and as
far as I know it currently doesn't work well with threads.  I'll work to
get it more feature-full during the summer.

PM


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: ltrace

[Sami Wagiaalla]

Petr Machata wrote:
> Hi,
>
> I committed first stab on ltrace for frysk, dubbed fltrace.
Sweet!

Re: ltrace

[Andrew Cagney]

Cool.

Have you considered folding this this to the current ftrace program so 
we've a tool that can trace both syscalls and library functions?

As an aside, the direction here is for ftrace to, by default, just 
report trace process fork/clone events.  Then if the user specifies 
syscalls (or library calls) to trace then it enables them.

Andrew

Petr Machata wrote:
> Hi,
>
> I committed first stab on ltrace for frysk, dubbed fltrace.  The output
> is very rudimentary, but should at least print out library function
> called from the executable itself.
>
> fltrace is only known to work on i386 for non-PIE ELF binaries, and as
> far as I know it currently doesn't work well with threads.  I'll work to
> get it more feature-full during the summer.
>
> PM
>
>   

Re: ltrace

[Petr Machata]

Andrew Cagney wrote:
> Cool.
> 
> Have you considered folding this this to the current ftrace program so
> we've a tool that can trace both syscalls and library functions?

Yes, I have.  I mostly wanted to get familiar with the framework, so I
made it tool on its own.  I will work on merging the two, fltrace is
mostly copied from ftrace anyway.

Btw, does it make sense, or is it feasible from frysk's architecture
standpoint, to add libcall event to frysk monitor?  (That gui thing with
time axis and ticks.)  I haven't done any investigation in this matter,
it just sits at the back of my brain since I started tinkering with frysk...

PM

Re: ltrace

[Sami Wagiaalla]

> Btw, does it make sense, or is it feasible from frysk's architecture
> standpoint, to add libcall event to frysk monitor?  (That gui thing with
> time axis and ticks.)  I haven't done any investigation in this matter,
> it just sits at the back of my brain since I started tinkering with frysk...
>   
Yes! for sure... it would give you a chance to explore that code; I 
would love to hear comments about that api. But if you want me to do it 
just file a bug.

Sami Wagiaalla

Re: ltrace

[Petr Machata]

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

Sami Wagiaalla wrote:
> Yes! for sure... it would give you a chance to explore that code; I
> would love to hear comments about that api. But if you want me to do it
> just file a bug.

Nice, will take a look at this later.  I'll reach you on chat if I have
more concrete questions.

> Sami Wagiaalla

PM


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]