MAN page from Other ptt-beta2.i386.rpm

PTT-VIEW

Section: (1)
Updated: 2005-05-12
Index

NAME

ptt-view - PTT raw and textual decoder

SYNOPSIS

ptt-view [options] input_file

DESCRIPTION

Its primary function is to decode the binary data collected by ptt-trace in a raw or textual format.

OPTIONS

Input options

-i file: input file name
The input file can also be the last command line option.

Output options

-o file

output file name

If it is `-' or not set, stdin will be used.

-r

raw export

This format can easily be parsed by external tools like grep, awk, cut, ...

-t

text export.

This format is more human friendly by providing the meaning of the arguments.

-s {pid,pidx,tid}

split output by pid or tid.

pid : each pid has its own file. The file pattern is filename-pid.

pidx : each pid has its own file and the history of the parent process is copied (doesn't work well as threads are deleted after a fork...) after a fork. The file pattern is filename-pid.

tid : each (pid, tid) couple has its own file. The file pattern is filename-pid-tid.

Warning : fork is problematic...

Filter options

-e pattern[,pattern...]

search for pattern* events.

It allows you to match the beginning of the event name and select a category of object. For example, you can select all the events related to mutexes with `-e MUTEX'.

The comma separator acts like an or, so you can filter multiple objects. For example, if you want mutex and cond-var, use `-e MUTEX,COND'.

You can repeat the option and the command line, but the result is a and, so only the names that are repeated will be displayed.

-E pattern[,pattern...]

search for *pattern events

It allows you to match the end of the event name. Like -e, the comma separator acts like an or.

For example, to select input/output, you can use `-E _IN,_OUT'.

-p pid[,pid...]

search for pid

select only events of the given pids

The comma acts like an or.

Warning : some mutex, cond-var could be initialised in another process (not a selected pid) or some object could be shared between process. So you could see strange results.

-n name[,name...]

select the objects by their name (actually address)

The comma acts like an or.

Warning : sometimes you could get strange results. It selects only the name of the current object and its properties, but sometimes there are some consistency problems. For example if you select a mutex name that is used by cond-var, you will see all the mutex operations, but not all the cond-var operations. This could be resolved by extending the function that gives a name to an object in order to manage more than one name, but it's actually not planned. A workaround is to selected all the object's names (here mutex + cond var).

There a similar problem after a fork for few events of the child. For example, we could wait for a cond wait, then fork. For the father there will be no problem, but the child won't have the cond wait out with a name.

-z start:end

event filter

This filter only displays "end - start" events skipping "start" events

The styntax -z :end or -z start: is also supported and imply start=0 or end=infinity.

Warning : the filter is applied to a group of events for performance issue, so the count is not always exact. You can have up to 3 more events than requested.

-Z start:end

time filter

This filter only displays events that occurred after "start" microseconds and before "end" microseconds.

The styntax -Z :end or -Z start: is also supported and imply start=0 or end=infinity.

Display options

-m: don't display the pid
-d: display the pid (this is the default option)
-h: display all the ptt-view commands

AUTHOR

Matthieu CASTET

This document was created byman2html,using the manual pages.