From: Petr Machata <pmachata@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: ltrace
Date: Thu, 26 Jul 2007 20:43:00 -0000 [thread overview]
Message-ID: <46A90812.2040208@redhat.com> (raw)
In-Reply-To: <46A8D56E.7040103@redhat.com>
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
next prev parent reply other threads:[~2007-07-26 20:43 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 ` ltrace Andrew Cagney
2007-07-26 20:43 ` Petr Machata [this message]
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=46A90812.2040208@redhat.com \
--to=pmachata@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
/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).