Project

General

Profile

Bug #574

lttng 2.2.0-rc2: reliable crash

Added by Daniel U. Thibault almost 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
High
Target version:
Start date:
06/25/2013
Due date:
% Done:

0%

Estimated time:

Description

Here is a reliable way of crashing LTTng:

$ sudo -H lttng create sss
Session sss created.
Traces will be written in /root/lttng-traces/sss-20130625-103225
$ sudo -H lttng enable-channel u0 -u --buffers-uid
UST channel u0 enabled for session sss
$ sudo -H lttng enable-channel k0 -k
Kernel channel k0 enabled for session sss
$ sudo -H lttng start
Tracing started for session sss
$ sudo -H lttng stop
Waiting for data availability
Tracing stopped for session sss
$ sudo -H lttng enable-channel u4 -u --buffers-uid
UST channel u4 enabled for session sss
$ sudo -H lttng start
Tracing started for session sss
$ sudo -H lttng enable-channel u6 -u --buffers-uid --subbuf-size 4096
UST channel u6 enabled for session sss
$ sudo -H lttng stop

At which point LTTng hangs and must be killed manually. Once the session daemon is killed, the "Waiting for data availability" message appears, followed by an awful lot of periods.

I'm using:
lttng-modules-2.2.0-rc2-11-5ca7b8a
lttng-tools 2.2.0-rc2-73-51fedb7
lttng-ust-2.2.0-rc2-34-76aca78
userspace-rcu-0.7.6-50-2f49a49


Files

bug-574.txt (27.2 KB) bug-574.txt lttng-sessiond -vvv ---verbose-consumer Daniel U. Thibault, 06/25/2013 01:26 PM

Also available in: Atom PDF