Project

General

Profile

Actions

Bug #826

closed
CB CB

Cannot enable-event twice even if tracing stopped.

Bug #826: Cannot enable-event twice even if tracing stopped.

Added by Christian Babeux over 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
High
Assignee:
Christian Babeux
Target version:
Start date:
08/18/2014
Due date:
% Done:

100%

Estimated time:

Description

While playing with JUL I stumbled upon this limitation:

$ lttng create foo
$ lttng enable-event -a -u
$ lttng start
[...]
$ lttng stop
$ lttng view
[...]
#
# Oops can't see JUL events, let's enable JUL domain...
#
$ lttng enable-event -a -j
Error: Events: Tracing already started (channel channel0, session foo)
Error: Command error

Is this an expected behavior?

DG Updated by David Goulet about 11 years ago Actions #1

  • Status changed from New to Confirmed
  • Assignee set to David Goulet
  • Priority changed from Normal to High
  • Target version set to 2.4

DG Updated by David Goulet about 11 years ago Actions #2

  • Status changed from Confirmed to Feedback

So this is because with "-a -j", we need to enable a new channel but a new channel CAN NOT be enabled after start. This is a limitation from the tracer.

I'm not sure how to fix that except a better error message?

CB Updated by Christian Babeux about 11 years ago Actions #3

  • Assignee changed from David Goulet to Christian Babeux

CB Updated by Christian Babeux about 11 years ago Actions #4

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100

Applied in changeset tools|commit:45d5d421f3464b541315509ecc2295be81b7139d.

Actions

Also available in: PDF Atom