Actions
Bug #830
closed
JG
enable-event command reports an error when successfully adding a probe
Bug #830:
enable-event command reports an error when successfully adding a probe
Start date:
08/21/2014
Due date:
% Done:
100%
Estimated time:
Description
"lttng enable-event -k test2 --probe sys_read+0x0" reports an error even though a probe was added successfully. The error message is not printed in "MI" mode.
$ lttng --mi xml enable-event -k test --probe sys_read+0x0
<?xml version="1.0" encoding="UTF-8"?>
<command><name>enable-event</name><output><events><event><name>test</name><type>PROBE</type><enabled>true</enabled><filter>false</filter><offset>0</offset><symbol_name>sys_read</symbol_name><success>true</success></event></events></output><success>true</success></command>
$ lttng enable-event -k test2 --probe sys_read+0x0
Kernel event test2 created in channel channel0
Error: Undefined command
$ lttng list auto-20140821-164128
Tracing session auto-20140821-164128: [inactive]
Trace path: /home/julien/lttng-traces/auto-20140821-164128
=== Domain: Kernel ===
Channels:
-------------
- channel0: [enabled]
Attributes:
overwrite mode: 0
subbufers size: 262144
number of subbufers: 4
switch timer interval: 0
read timer interval: 200000
trace file count: 0
trace file size (bytes): 0
output: splice()
Events:
test2 (type: probe) [enabled]
offset: 0x0
symbol: sys_read
test (type: probe) [enabled]
offset: 0x0
symbol: sys_read
JR Updated by Jonathan Rajotte about 11 years ago
Target version is not the good one. v2.5.0 is not affected by the bug.
And in bonus see patch for resolution:
http://lists.lttng.org/pipermail/lttng-dev/2014-August/023468.html
JG Updated by Jérémie Galarneau about 11 years ago
- Target version changed from 2.5 to 2.4
JR Updated by Jonathan Rajotte about 11 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset tools|commit:fbdb7e15cbe6235cadaaa7c1b2213f128e747e47.
Actions