public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: tthomas@sourceware.org
To: frysk-cvs@sourceware.org
Subject: [SCM]  master: Add watch command to news file.
Date: Wed, 16 Apr 2008 15:14:00 -0000	[thread overview]
Message-ID: <20080416151405.14248.qmail@sourceware.org> (raw)

The branch, master has been updated
       via  c2385ede8804d05066966d97177cbcf4fcfaed19 (commit)
      from  641ed177f921ccaa93d7086b54fe64fa3bdb5b00 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit c2385ede8804d05066966d97177cbcf4fcfaed19
Author: Teresa Thomas <tthomas@redhat.com>
Date:   Wed Apr 16 07:11:54 2008 -0400

    Add watch command to news file.
    
    frysk-top/ChangeLog:
    2008-04-16  Teresa Thomas  <tthomas@redhat.com>
    
            * NEWS: Update - add watch command.

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

Summary of changes:
 NEWS                |   31 +++++++++++++++++++++----------
 frysk-top/ChangeLog |    4 ++++
 2 files changed, 25 insertions(+), 10 deletions(-)

First 500 lines of diff:
diff --git a/NEWS b/NEWS
index 6ab8e5e..3c3dd0a 100644
--- a/NEWS
+++ b/NEWS
@@ -9,6 +9,17 @@ and C++.  It is aimed at providing developers and system
 administrators with the ability to examine and analyze multi-host,
 multi-process, and multi-threaded systems while they are running.
 
+--
+
+Post-Release 0.2 Updates:
+
+-> 2004-04-16 - New command in FHPD: watch
+
+   Use to set watchpoints on expressions or variables. This stops
+   program execution when memory location associated with the
+   expression is written to or read from.
+
+--
 
 Release 0.2, 2008-04-02:
 
@@ -16,17 +27,17 @@ This initial release of frysk includes:
 
 -> command line utilities:
 
-   fauxv - print the auxiliary vector (new)
-   fcatch - catch and print the stack of a crashing process
-   fcore - extract a core file from a running process (faster, more correct)
+   fauxv      - print the auxiliary vector (new)
+   fcatch     - catch and print the stack of a crashing process
+   fcore      - extract a core file from a running process (faster, more correct)
    fdebuginfo - list debug-info requirements of a process (new)
-   fdebugrpm - install debug-info requirements of a process (new)
-   ferror - catch and back-trace error calls (new)
-   fexe - print the executable path
-   fmaps - print the address map (new)
-   fstack - print each thread's stack (supports in-line back-traces)
-   fstep - single-step a process
-   ftrace - trace a processes system and (new) library calls
+   fdebugrpm  - install debug-info requirements of a process (new)
+   ferror     - catch and back-trace error calls (new)
+   fexe       - print the executable path
+   fmaps      - print the address map (new)
+   fstack     - print each thread's stack (supports in-line back-traces)
+   fstep      - single-step a process
+   ftrace     - trace a processes system and (new) library calls
 
    Known limitations: large resident set size; large executable size.
 
diff --git a/frysk-top/ChangeLog b/frysk-top/ChangeLog
index e34b7f6..f48b197 100644
--- a/frysk-top/ChangeLog
+++ b/frysk-top/ChangeLog
@@ -1,3 +1,7 @@
+2008-04-16  Teresa Thomas  <tthomas@redhat.com>
+
+	* NEWS: Update - add watch command.
+
 2008-04-08  Andrew Cagney  <cagney@redhat.com>
 
 	* Makefile.am (javadoc): Use frysk-common/javadocs.sh.


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


                 reply	other threads:[~2008-04-16 15:14 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=20080416151405.14248.qmail@sourceware.org \
    --to=tthomas@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).