Project

General

Profile

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)

Added by Leo Jweda almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Critical
Assignee:
-
Target version:
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

#1

Updated by Mathieu Desnoyers almost 4 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.

#2

Updated by Leo Jweda almost 4 years ago

My apologies. We use

lttng enable-event -u -all

just before lttng start.

We will post a video of the behaviour and how to reproduce shortly.

#3

Updated by Leo Jweda almost 4 years ago

Here's a video of how to reproduce the bug, the expected results, and the actual results: https://www.youtube.com/watch?v=OIlqDdWTdEE

#4

Updated by Mathieu Desnoyers almost 4 years ago

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

Applied in changeset babeltrace:babeltrace|commit:220e0cbec97669ccfe4ed8a7e69c73c9ac72062d.

Also available in: Atom PDF