Project

General

Profile

Actions
Copy link

Bug #938

open
JR

Enabling two events with same name but not the same event type cause no warning and does not behave as expected

Bug #938: Enabling two events with same name but not the same event type cause no warning and does not behave as expected

Added by Jonathan Rajotte Julien about 10 years ago. Updated about 8 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Target version:
LTTng - 2.10
Start date:
09/15/2015
Due date:
% Done:

0%

Estimated time:

Description

sudo lttng-sessiond -d
lttng create mysession
lttng enable-event --kernel kmem_kfree --probe sys_open+0xE
lttng enable-event --kernel kmem_kfree
lttng start
sleep 0.1
lttng stop
lttng view

Only the probe is considered when tracing. The metadata only shows the probe event.

This is a kernel tracer side problem (name as event key). A solution could be to prefix certain type of event on enable thus creating namespace e.g: probe_kmem_kfree.

JG Updated by Jérémie Galarneau over 9 years ago Actions
Copy link
 #1

  • Project changed from LTTng to LTTng-modules
  • Target version changed from 2.8 to 2.9

Assigning to LTTng-modules as per the bug description. I have not checked if this is an lttng-modules or lttng-tools limitation (using only the name as the key vs. a tuple of type+name+...).

MD Updated by Mathieu Desnoyers almost 9 years ago Actions
Copy link
 #2

  • Target version changed from 2.9 to 2.10

FD Updated by Francis Deslauriers about 8 years ago Actions
Copy link
 #3

I also faced that issue with the following commands with --function event type:

lttng enable-event -k --function=sys_open sched_switch
lttng enable-event -k --probe=sys_read sched_switch
lttng enable-event -k sched_switch

Actions
Copy link

Also available in: PDF Atom