Project

General

Profile

Actions

Bug #690

closed

lttng man pages too restrictive with respect to when filters can be defined

Added by Daniel U. Thibault almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
Start date:
11/19/2013
Due date:
% Done:

0%

Estimated time:

Description

The lttng 2.3 man pages still claim that "Filter only allowed when enabling events within a session before tracing is started."

That is not true, you can enable new events with filters while the trace is running.

Actions #1

Updated by David Goulet almost 11 years ago

  • Status changed from New to Resolved

Fixed with commit: 7b4572b71d29a35d7408d0a25913990573fd80c0

Actions #2

Updated by Daniel U. Thibault almost 11 years ago

That commit did not resolve this bug. According to http://git.lttng.org/?p=lttng-tools.git;a=blobdiff;f=doc/man/lttng.1;h=0f9cd9c516b3a3fbc4955643ab1e6e4885babc61;hp=659a27c66eb8d0fb09cb0f6f5f34daf209c06038;hb=7b4572b71d29a35d7408d0a25913990573fd80c0;hpb=5a5b4330b2bc140e22d9971a0697236e1cecf330 it changed the man page to read:

.BR "\-\-filter 'expression'" 
 Set a filter on a newly enabled event. Filter expression on event
 fields and context. The event will be recorded if the filter's
 expression evaluates to TRUE. Only specify on first activation of a
 given event within a session.
 Specifying a filter is only allowed when enabling events within a session before
 tracing is started. If the filter fails to link with the event
 within the traced domain, the event will be discarded.
 Filtering is currently only implemented for the user-space tracer.

The sentence "Specifying a filter is only allowed when enabling events within a session before tracing is started." should be deleted.

Actions

Also available in: Atom PDF