Project

General

Profile

Feature #15

LTTng simple trace

Added by Matthew Khouzam over 8 years ago. Updated over 4 years ago.

Status:
Confirmed
Priority:
Low
Assignee:
-
Target version:
Start date:
03/30/2012
Due date:
02/10/2013 (over 7 years late)
% Done:

0%

Estimated time:
0.00 h

Description

Requesting a new command in lttng-tools
the name should be something like trace and the functionality should be similar to strace.
the syntax could be something like
lttng trace program_name program_args
let's say you instrumented ls, then lttng trace ls -l /dev would trace ls going through the directory.
The traces taken should be both kernel and UST unless otherwise specified.
The timestamps for user space and kernel space should be on the same base. (Offsets will make this unusable by most)
the command sequence internally could be as simple as
lttng create default_name; lttng enable-event -a -k ; lttng enable-event -a -u; lttng start; %program_name; lttng stop; lttng destroy;
If the person is not in the tracing group or root, the kernel trace should be unavailable with a warning. if the application is not instrumented, it should warn too. if the kernel and userspace tracer is not available, it should warn that too but still run.

These ideas are very open for discussion


Related issues

Blocked by LTTng - Feature #34: Flight-recorder modeResolved02/11/2012

Actions
Blocked by Babeltrace - Feature #31: Add "live" trace reading supportResolved02/11/2012

Actions

Also available in: Atom PDF