public inbox for frysk-cvs@sourceware.org help / color / mirror / Atom feed
From: cagney@sourceware.org To: frysk-cvs@sourceware.org Subject: [SCM] master: Merge in NEWS file. Date: Wed, 02 Apr 2008 16:29:00 -0000 [thread overview] Message-ID: <20080402162859.4888.qmail@sourceware.org> (raw) The branch, master has been updated via 21e0b3aa7264d3aab652e4a59e804d4114235b1c (commit) via 72f2cd3e8b912a1c8cf490bc40a38325d4c131c1 (commit) from 67ca0747166b7e823d4f9f2f1b8f581c01be2735 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 21e0b3aa7264d3aab652e4a59e804d4114235b1c Merge: 72f2cd3e8b912a1c8cf490bc40a38325d4c131c1 67ca0747166b7e823d4f9f2f1b8f581c01be2735 Author: Andrew Cagney <cagney@redhat.com> Date: Wed Apr 2 12:27:30 2008 -0400 Merge in NEWS file. commit 72f2cd3e8b912a1c8cf490bc40a38325d4c131c1 Author: Andrew Cagney <cagney@redhat.com> Date: Wed Apr 2 12:26:33 2008 -0400 frysk-top/ChangeLog 2008-04-02 Andrew Cagney <cagney@redhat.com> * NEWS: Seed. ----------------------------------------------------------------------- Summary of changes: NEWS | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++ frysk-top/ChangeLog | 4 +++ 2 files changed, 61 insertions(+), 0 deletions(-) create mode 100644 NEWS First 500 lines of diff: diff --git a/NEWS b/NEWS new file mode 100644 index 0000000..6ab8e5e --- /dev/null +++ b/NEWS @@ -0,0 +1,57 @@ + + Frysk + ----- + + http://sourceware.org/frysk/ + +Frysk is an execution-analysis technology being developed using Java +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. + + +Release 0.2, 2008-04-02: + +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) + 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 + + Known limitations: large resident set size; large executable size. + +-> Prototype command line debugger: fhpd + + For single threaded programs, FHPD can: print the value, type, and + location, and modify the value of, arbitrarily located variable + (complex DWARF location expressions); correctly handle very-large + integers (>64-bit) and large floats (80-bit); display in-line + information in back-traces; control processes with the commands + load, core, dump, run, step, break, go, detach, kill, list, focus. + + In addition to the command-line utility restrictions, the HPD has + the following known limitations: disassembler missing; limited + type-cast support in expressions; limited multi-thread support. + +-> Prototype visual debugging and monitoring tool (frysk) + + Known limitations: work-flow limited to live processes (examining + core files, or creating processes is possible but very + non-intuitive). + +-> Prototype test-suite (funit) + + Known limitations: test that are working in-tree fail when + installed. + +-- diff --git a/frysk-top/ChangeLog b/frysk-top/ChangeLog index 3f68aee..206efa1 100644 --- a/frysk-top/ChangeLog +++ b/frysk-top/ChangeLog @@ -1,3 +1,7 @@ +2008-04-02 Andrew Cagney <cagney@redhat.com> + + * NEWS: Seed. + 2008-03-31 Andrew Cagney <cagney@redhat.com> * Makefile.am (upload-manpages): Explicitly depend on hooks/post-receive -- frysk system monitor/debugger
reply other threads:[~2008-04-02 16:29 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=20080402162859.4888.qmail@sourceware.org \ --to=cagney@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: linkBe 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).