From: Sami Wagiaalla <swagiaal@redhat.com>
To: Petr Machata <pmachata@redhat.com>
Cc: Andrew Cagney <cagney@redhat.com>, frysk <frysk@sourceware.org>
Subject: Re: ltrace
Date: Fri, 27 Jul 2007 14:40:00 -0000 [thread overview]
Message-ID: <46AA03CB.50008@redhat.com> (raw)
In-Reply-To: <46A90812.2040208@redhat.com>
> 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
next prev parent reply other threads:[~2007-07-27 14:40 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 ` ltrace Petr Machata
2007-07-27 14:40 ` Sami Wagiaalla [this message]
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=46AA03CB.50008@redhat.com \
--to=swagiaal@redhat.com \
--cc=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).