Bug #1258
openSegmentation fault when running with --debug
0%
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 bt_plugin_so_init@plugin-so.c: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 bt_current_thread_take_error@current-thread.c:30 Took current thread's error object: addr=(nil)
04-22 16:23:37.188 97664 97664 I LIB/MESSAGE-ITERATOR-CLASS bt_message_iterator_class_create@message-iterator-class.c:61 Creating message iterator class: next-method-addr=0x7f066675e3b0
04-22 16:23:37.188 97664 97664 D LIB/CUR-THREAD bt_current_thread_take_error@current-thread.c:30 Took current thread's error object: addr=(nil)
04-22 16:23:37.188 97664 97664 D LIB/MESSAGE-ITERATOR-CLASS bt_message_iterator_class_set_initialize_method@message-iterator-class.c:89 Set message iterator class's iterator initialization method: addr=0x564bd652ac60
04-22 16:23:37.188 97664 97664 D LIB/CUR-THREAD bt_current_thread_take_error@current-thread.c:30 Took current thread's error object: addr=(nil)
04-22 16:23:37.188 97664 97664 D LIB/MESSAGE-ITERATOR-CLASS bt_message_iterator_class_set_finalize_method@message-iterator-class.c:104 Set message iterator class's finalization method: addr=0x564bd652ac60
04-22 16:23:37.188 97664 97664 D LIB/CUR-THREAD bt_current_thread_take_error@current-thread.c: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
Updated by Simon Marchi over 4 years ago
Proposed patch: https://review.lttng.org/c/babeltrace/+/3450