Project

General

Profile

Actions
Copy link

Bug #943

closed

All events are filtered-out when using a wildcard in a filter's criterion

Added by Jérémie Galarneau about 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Mathieu Desnoyers
Target version:
LTTng - 2.7
Start date:
09/29/2015
Due date:
% Done:

100%

Estimated time:

Description

While applying a filter to syscalls of the form:

$ lttng enable-event --kernel --syscall --all --filter 'filename == "*"'

[12:46:10.047113455] (+0.009323468) XThink syscall_entry_open: { cpu_id = 1 }, { filename = "/home/jgalar/.config/chromium/Default", flags = 524288, mode = 420 }
[12:46:10.615910212] (+0.568796757) XThink syscall_entry_open: { cpu_id = 2 }, { filename = "/home/jgalar/.config/chromium/Default/.org.chromium.Chromium.nMsMbS", flags = 194, mode = 384 }
[12:46:10.615965534] (+0.000055322) XThink syscall_entry_open: { cpu_id = 2 }, { filename = "/home/jgalar/.config/chromium/Default/.org.chromium.Chromium.nMsMbS", flags = 1, mode = 384 }

works, it seems that a more complex string results in no events being traced.

$ lttng enable-event --kernel --syscall --all --filter 'filename == "/home/jgalar*"'

... no events!
Actions
Copy link

Also available in: Atom PDF