public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: Announcing frysk 0.2.1
Date: Sun, 06 Apr 2008 07:12:00 -0000	[thread overview]
Message-ID: <47F6908B.1010807@redhat.com> (raw)

                        Announcing Frysk 0.2.1
                        ----------------------
                     http://sourceware.org/frysk/

Frysk is a debugging and monitoring framework 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.

We, that is, Adam Jocksch, Alexandre Oliva, Andrew Cagney, Carlos
Eduardo Seo, Chris Moller, Diego Novillo, Elena Zannoni, Frank
Ch. Eigler, Igor Foox, Ivan Pantuyev, Jan Kratochvil, Jeff Johnston,
Jose Flavio Paulino, Kris Van Hees, Len DiMaggio, Mark Wielaard, Mike
Behm, Mike Cvet, Nurdin Premji, Petr Machata, Phil Muldoon, Richard
Henderson, Rick Moseley, Sami Wagiaalla, Stan Cox, Stepan Kasal, Tarun
Khanna, Teresa Thomas, Thomas Gerard, Tim Moore, Tom Tromey, Wu Zhou,
Yao Qi, Yong Zheng, and Zhao Shujing are pleased to announce our first
official release of Frysk, version 0.2.1.

This initial release 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: some test that are working in-tree fail when
   installed.

To download this release, go to:

             ftp://sourceware.org/pub/frysk/frysk-0.2.1.tar.bz2

or check for an update in your local GNU/Linux distro.

Andrew
2008-04-04

                 reply	other threads:[~2008-04-04 20:33 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=47F6908B.1010807@redhat.com \
    --to=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).