Re: GUADEC proposal

[Sami Wagiaalla <swagiaal at redhat dot com>]

Okay here is take two of the proposal after
much appreacicated feedback from Andrew and Michael Behm.

_*Title*_

Frysk: an Execution Analysis Tool

_*Track*_

“The *Topaz* track will contain visions, guesses, plans, alpha 
developments and anything related to the future.”

I think the Topaz is a better fit for us :).

_*Point of View*_

*“The Developer*. Sessions about... development :), languages, 
platforms, libraries, standards, bugs and the GNOME project workflow. 
Closure and social event at the end, with a possibility of a KDE-GNOME 
rematch, this time on basketball.”

_*Type of Session:*_

15' presetation.

_*Summary*_

Frysk is a new object oriented execution analysis tool written in Java 
using the Java-GNOME bindings. The goal of Frysk is to solve usability, 
and functionality problems with traditional debugging, making it 
possible to debug and analyze large scale multi threaded applications.

_*Full Description*_

Frysk is an execution analysis tool. The Frysk core creates and 
maintains an event-driven, interactive Domain Object Model of the 
operating environment and its composing elements. These elements include 
hosts, processes and threads, and language models for those processes 
and threads. The model allows clients of that API to observe, analyze, 
and manipulate its elements.

Frysk uses this model to enable developers and system administrators to 
solve higher-level problems such as monitoring the execution of a 
system, monitoring the use of locking primitives, exposing deadlocks, 
gathering data, debugging multi threaded applications, and even catching 
problems that might involve more than one process.

Frysk is also intended as an always-on monitoring tool that allows the 
user to set up observers to catch certain problems and get a chance to 
analyze them as soon as they occurs –while the process is still alive.

The Frysk GUI is designed to provide users with high level view, hiding 
away noisy, intricate details until they are requested. This high level 
overview, in combination with correct and live modeling of
a problem, is what programmers seek when they choose the use of print 
statements and avoid traditional debuggers.