Project

General

Profile

Bug #1258

Segmentation fault when running with --debug

Added by Geneviève Bastien 7 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
04/22/2020
Due date:
% Done:

0%

Estimated time:

Description

When running babeltrace2 with the --debug flag for a CTF trace, babeltrace segfaults with last messages being:

04-22 16:23:37.188 97664 97664 I LIB/PLUGIN-SO :761 Creating and setting properties of plugin's component class: plugin-path="/usr/local/lib/babeltrace2/plugins/babeltrace-plugin-ctf.la", plugin-name="ctf", comp-class-name="fs", comp-class-type=SOURCE
04-22 16:23:37.188 97664 97664 D LIB/CUR-THREAD :30 Took current thread's error object: addr=(nil)
04-22 16:23:37.188 97664 97664 I LIB/MESSAGE-ITERATOR-CLASS :61 Creating message iterator class: next-method-addr=0x7f066675e3b0
04-22 16:23:37.188 97664 97664 D LIB/CUR-THREAD :30 Took current thread's error object: addr=(nil)
04-22 16:23:37.188 97664 97664 D LIB/MESSAGE-ITERATOR-CLASS :89 Set message iterator class's iterator initialization method: addr=0x564bd652ac60
04-22 16:23:37.188 97664 97664 D LIB/CUR-THREAD :30 Took current thread's error object: addr=(nil)
04-22 16:23:37.188 97664 97664 D LIB/MESSAGE-ITERATOR-CLASS :104 Set message iterator class's finalization method: addr=0x564bd652ac60
04-22 16:23:37.188 97664 97664 D LIB/CUR-THREAD :30 Took current thread's error object: addr=(nil)
[1] 97664 segmentation fault (core dumped)

Reproducible on archlinux and ubuntu, with or without the BABELTRACE_DEBUG_MODE enabled

#1

Updated by Simon Marchi 7 months ago

Confirmed.

Also available in: Atom PDF