Project

General

Profile

Bug #1096

Babeltrace takes 100% CPU and 100% mem reading a malformed trace

Added by Francis Deslauriers almost 4 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
04/21/2017
Due date:
% Done:

0%

Estimated time:

Description

Babeltrace Version: 1.5.2
While hacking on the LTTng kernel tracer, I mistakenly wrote a ctf_sequence with 1 element but a length of 0 resulting in a malformed trace.
When reading the malformed trace, Babeltrace hangs and takes 100% of one CPU and 100% of the available memory.

I attached the trace in question.


Files

auto-20170421-164755.tar.gz (115 KB) auto-20170421-164755.tar.gz Francis Deslauriers, 04/21/2017 09:12 PM
trace-fdpf-20190524-165653.tar.gz (30.9 KB) trace-fdpf-20190524-165653.tar.gz Trace with sequence too big in channel0_7 first event Geneviève Bastien, 05/24/2019 04:07 PM

Also available in: Atom PDF