Bug #826
closed
Cannot enable-event twice even if tracing stopped.
Added by Christian Babeux over 9 years ago.
Updated over 9 years ago.
Assignee:
Christian Babeux
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?
- Status changed from New to Confirmed
- Assignee set to David Goulet
- Priority changed from Normal to High
- Target version set to 2.4
- 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?
- Assignee changed from David Goulet to Christian Babeux
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Applied in changeset tools|commit:45d5d421f3464b541315509ecc2295be81b7139d.
Also available in: Atom
PDF