Bug #1010: When babeltrace (and lttng view) output is redirected from stdout while receiving live traces it does not print events as they come in (using > not --output since --output doesn't work) - LTTng - LTTng bugs repository

Actions

Copy link

Bug #1010

closed

When babeltrace (and lttng view) output is redirected from stdout while receiving live traces it does not print events as they come in (using > not --output since --output doesn't work)

Added by Leo Jweda about 8 years ago. Updated about 8 years ago.

Status:

Resolved

Priority:

Critical

Assignee:

Target version:

2.6

Start date:

04/19/2016

Due date:

% Done:

100%

Estimated time:

Description

Components involved: babeltrace and lttngview
Component version: How do you get babeltrace's version!? LTTng version: 2.6.0
System information: Linux leojweda-VirtualBox 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15 22:15:45 UTC 2016 x86_64 x86_64 GNU/Linux
Expected results: When running "lttng view > someFile" the events get written to the file as they come in. See how redirecting output to a file works with ping.
Actual results: The events get dumped to the file after about a minute or two, or when the session ends. It works fine if the output is left to stdout.
Steps to reproduce:

lttng create Failover --live
lttng start
./testSystemMain

(in a different terminal)

lttng view

Actions

Copy link

Updated by Mathieu Desnoyers about 8 years ago

You appear to have missed the "enable-event" step, which means there is nothing traced. Therefore, lttng view is sitting there awaiting for events, but none are produced.

Actions

Copy link