Frysk presentation

Frysk presentation

[Sami Wagiaalla]

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

I gave a presentation on frysk to the Toronto office to encourage people 
to use it, and hopefully get some feed back. And also, get some practice 
in giving presentations :)

I have attached the slides. The slides are sparse but you should find 
more information in the notes section of each slide.

Although I demoed a lot of fhpd and the command line utilities. I have 
proposed two command line utilities for attendees to use: fcatch and 
ferror. In hindsight i should have also included ftrace.

The idea was to isolate and identify functionality in frysk which solve 
user problems did them well and was distinguishably better than the 
alternative.

Overall I think that the talk was informative in educating people about 
what frysk is and what its goals are. I think attendees can now answer 
questions about frysk if asked. And I pexpect that we will get 1 or 2 
users from the attendees which is around 10%.

More specifically behdad was excited about ftrace and has made some 
specific requests:
- To be able to easily specify which library he wants traced
- To be able to trace private functions.
- To be able to tell frysk how to print cairo types.

Sami

[-- Attachment #2: FryskLunch&Learn.sxi --]
[-- Type: application/vnd.sun.xml.impress, Size: 108157 bytes --]

Frysk presentation

[Sami Wagiaalla]

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

I gave a presentation on frysk to the Toronto office to encourage people
to use it, and hopefully get some feed back. And also, get some practice
in giving presentations :)

I have attached the slides. The slides are sparse but you should find
more information in the notes section of each slide.

Although I demoed a lot of fhpd and the command line utilities. I have
proposed two command line utilities for attendees to use: fcatch and
ferror. In hindsight i should have also included ftrace.

The idea was to isolate and identify functionality in frysk which solve
user problems did them well and was distinguishably better than the
alternative.

Overall I think that the talk was informative in educating people about
what frysk is and what its goals are. I think attendees can now answer
questions about frysk if asked. And I pexpect that we will get 1 or 2
users from the attendees which is around 10%.

More specifically behdad was excited about ftrace and has made some
specific requests:
- To be able to easily specify which library he wants traced
- To be able to trace private functions.
- To be able to tell frysk how to print cairo types.

Sami


[-- Attachment #2: FryskLunch&Learn.sxi --]
[-- Type: application/vnd.sun.xml.impress, Size: 108157 bytes --]

Re: Frysk presentation

[Petr Machata]

[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]

Sami Wagiaalla wrote:
> More specifically behdad was excited about ftrace and has made some
> specific requests:
> - To be able to easily specify which library he wants traced
Tracked here: http://sourceware.org/bugzilla/show_bug.cgi?id=5850

> - To be able to trace private functions.
What does this mean?  Is it like he wants to request tracing of private
methods of some class?  E.g. something like:
  -sym='\private(someclass::*@libsoname.*)'
(The \private qualifier doesn't work, I'm just playing around with some
syntax.)

Or if private function is just function not exported to dynamic symbol
table, that would be -sym='@libsoname.*', but then symbol table is
necessary.  This limitation is going to disappear once ftrace is
rewritten to use frysk own framework for breakpoint handling, instead of
reimplementing half of libdwfl on its own :)

> - To be able to tell frysk how to print cairo types.

... and for that matter, ftrace needs smarts to know what prototype a
function has, so that it can format the output accordingly, à la strace.
 Most of that can be derived from debuginfo, but not everything.
Sometimes 'unsigned int' is actually set of or-ed flags, or it accepts
some #defined constants, some pointers are actually return values, etc.
 This all should be possible to configure.

Ideally these configuration files would be distributed in devel
subpackage of the library whose interfaces it describes.

Also ideally the smarts that infer the prototype would be shared with
whoever needs them (dltrace and ltrace come to mind).

PM


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]