Bug #363
closedlttng attempts to disable event but failed to do so, corresponding trace log do not match with what is expected
100%
Description
Sceanrio: =========
/home/test_apps/demo-trace 60 &
lttng list -u
lttng create $SESSION_NAME -o /cluster/temp/sessiondir/$SESSION_NAME
lttng enable-event "ust_tests_demo2:l*" -u --filter ' intfield > 3'
lttng enable-event "ust_tests_demo2:loop" -u --filter ' intfield < 3'
Error: Invalid filter bytecode
Error: Setting filter for event ust_tests_demo2:loop: ' intfield < 3'
Error: UST app event ust_tests_demo2:loop disable failed for app (pid: 20616) and session handle 2 with ret -22
Error: Disabling event ust_tests_demo2:loop after filter error: Disable UST event failed
Why does it attempt to disable the second event ?NOTE that when the demo app is executed after the session is started, then there is no
error given and the expected result (below) is obtained.
If the demo app is running while the event is enabling, then the above error is given and
the result trace log do not match with what is expected.lttng start $SESSION_NAME;
lttng list $SESSION_NAME
#--- wait for demo to finish.
sleep 1
babeltrace --no-delta /cluster/temp/sessiondir/$SESSION_NAME
Result:
=======
- see only event with "intfield = 4" .
Expected Result:
================
- event with: intfield =0,1,2,4
Extra note:
===========
- This might be related to ust bug-362 .
When trying to use wildcard to enabling an event, the following
error is given on the terminal from where the demo app is running:
[lttng filter] error linking wildcard bytecode
This bug has been fixed by not showing the above error but it
looks like the after maths has not been clean up.It might be leading to sessiond coredump later (this will be
reported in a separated bug report to help us keeping track
of the issues).Files