public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: pmachata@sourceware.org
To: frysk-cvs@sourceware.org
Subject: [SCM] frysk system monitor/debugger branch, master, updated. 616c9bbb472fb0b0d23e4ae233c2f19926fe8d20
Date: Fri, 02 Nov 2007 16:42:00 -0000	[thread overview]
Message-ID: <20071102164233.23941.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "frysk system monitor/debugger".

The branch, master has been updated
       via  616c9bbb472fb0b0d23e4ae233c2f19926fe8d20 (commit)
      from  5fba661cfc4cfc9ba9712629ff9722f25e900f86 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 616c9bbb472fb0b0d23e4ae233c2f19926fe8d20
Author: Petr Machata <pmachata@redhat.com>
Date:   Fri Nov 2 16:51:55 2007 +0100

    New test for ltrace
    
    Testing whether arguments recorded at function call match reality, and that return values are as expected.

-----------------------------------------------------------------------

Summary of changes:
 frysk-core/frysk/ftrace/ChangeLog                  |    4 +
 frysk-core/frysk/ftrace/TestLtrace.java            |   89 +++++++++++++++++++-
 frysk-core/frysk/pkglibdir/ChangeLog               |    4 +
 .../{funit-syscallloop.c => funit-calls.c}         |   31 +++----
 4 files changed, 108 insertions(+), 20 deletions(-)
 copy frysk-core/frysk/pkglibdir/{funit-syscallloop.c => funit-calls.c} (83%)


hooks/post-receive
--
frysk system monitor/debugger


                 reply	other threads:[~2007-11-02 16:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20071102164233.23941.qmail@sourceware.org \
    --to=pmachata@sourceware.org \
    --cc=frysk-cvs@sourceware.org \
    --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).