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

Also available in: Atom PDF