Project

General

Profile

Actions
Copy link

Bug #348

closed
TL

SessionD becomes inresponsive after enabling event with filter (1>2)

Bug #348: SessionD becomes inresponsive after enabling event with filter (1>2)

Added by Tan le tran over 13 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Target version:
LTTng - 2.1 stable
Start date:
09/19/2012
Due date:
% Done:

0%

Estimated time:

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

terminal_log.txt (44.5 KB) terminal_log.txt Terminal log with "lttng-sessiond -vvv" Tan le tran, 09/19/2012 04:23 PM

DG Updated by David Goulet over 13 years ago Actions
Copy link
 #1

  • Status changed from New to Confirmed
  • Target version set to 2.1 stable

DG Updated by David Goulet over 13 years ago Actions
Copy link
 #2

  • Priority changed from Normal to High

DG Updated by David Goulet over 13 years ago Actions
Copy link
 #3

  • 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

TL Updated by Tan le tran over 13 years ago Actions
Copy link
 #4

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

DG Updated by David Goulet over 13 years ago Actions
Copy link
 #5

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: PDF Atom