From: Andrew Cagney <cagney@redhat.com>
To: Petr Machata <pmachata@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: ltrace
Date: Thu, 26 Jul 2007 17:09:00 -0000 [thread overview]
Message-ID: <46A8D56E.7040103@redhat.com> (raw)
In-Reply-To: <46A8B656.50906@redhat.com>
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
>
>
next prev parent reply other threads:[~2007-07-26 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 14:57 ltrace Petr Machata
2007-07-26 15:02 ` ltrace Sami Wagiaalla
2007-07-26 17:09 ` Andrew Cagney [this message]
2007-07-26 20:43 ` ltrace Petr Machata
2007-07-27 14:40 ` ltrace Sami Wagiaalla
2007-07-27 14:58 ` ltrace Petr Machata
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A8D56E.7040103@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=pmachata@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).