Bug #348
closedSessionD becomes inresponsive after enabling event with filter (1>2)
0%
Description
Commits used:
=============
userspace : (Thu Sep 6 ) a5a9f42 Ensure that read-side functions meet 10-line LGPL criterion
lttng-ust : (Tue Sep 18) 5d3bc5e Fix: get_wait_shm() ust mutex deadlock (add 2 missing exit calls)
lttng-tools:(Tue Sep 18) 4adabd6 Fix: Remove LPOLLNVAL from consumer metadata revents
babeltrace: (Thu Sep 13) f546472 Fix: Documentation cleanup
Scenario:
=========
1)_ Run demo app (comes with lttng-ust tree)
LTTNG_UST_DEBUG=1 ./demo-trace 70 &
2)_ lttng create $SESSION_NAME -o /cluster/temp/sessiondir/$SESSION_NAME
3)_ lttng enable-event ust_tests_demo2:loop -u --filter ' 1>2 '
SessionD hang !4)_ From another terminal, "lttng list" but no response from sessionD
Files
Updated by David Goulet about 12 years ago
- Status changed from New to Confirmed
- Target version set to 2.1 stable
Updated by David Goulet about 12 years ago
- Status changed from Confirmed to Feedback
Using the above scenario, I can NOT reproduce this bug. We got multiple filter fixes in the last month so one of them could have fix this.
Flagging this bug to Needs Feedback.
Tan, please let me know if this is still an issue or I'll close it in a couple of days if I don't get feedback.
Thanks
Updated by Tan le tran about 12 years ago
Hi David,
I believe that when verifying the fix of bug-342, I was not able to see the bug-348 since then.
So I guess you can close this one now.
Best Regards,
Tan
Updated by David Goulet about 12 years ago
- Status changed from Feedback to Resolved