Project

General

Profile

Actions
Copy link

Bug #261

closed

lttng_enable_event makes lttng freeze when then event is of type LTTNG_EVENT_ALL and with an unexisting name

Added by Danny Serres almost 12 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
High
Assignee:
David Goulet
Target version:
2.0.x stable
Start date:
06/07/2012
Due date:
% Done:

0%

Estimated time:

Description

if an event of type LTTNG_EVENT_ALL (-1) has a random name, such as "blabla", and lttng_enable_event is called with that event, it returns no error but it should.

As a result of this, for a session named "ses", lttng list ses will give: === Domain: Kernel ===

Channels:
-------------
- channel0: [enabled]

Attributes:
      overwrite mode: 0
      subbufers size: 262144
      number of subbufers: 4
      switch timer interval: 0
      read timer interval: 200
      output: splice()
Events:
       (loglevel: TRACE_EMERG (0)) (type: tracepoint) [disabled]

and then destroy all sessions.

If lttng list ses is not called, but instead the session is started, then it is goodbye lttng, see you next reboot.

Actions
Copy link
 #1

Updated by Yannick Brosseau almost 12 years ago

  • Project changed from LTTng to LTTng-tools
Actions
Copy link
 #2

Updated by David Goulet almost 12 years ago

  • Status changed from New to Confirmed
  • Assignee set to David Goulet
  • Priority changed from Normal to High
  • Target version set to 2.0.x stable
Actions
Copy link
 #3

Updated by David Goulet over 11 years ago

  • Status changed from Confirmed to Resolved

Fixed by commit 95a8266405f61b6927f8cef13b1fdfa0b5584274

Actions
Copy link

Also available in: Atom PDF