Actions
Bug #1389
opensrc.ctf.fs crash with invalid trace
Start date:
09/18/2023
Due date:
% Done:
0%
Estimated time:
Description
Using the attached trace, I get:
$ ./src/cli/babeltrace2 trace 09-18 16:15:58.978 335803 335803 E PLUGIN/CTF/MSG-ITER ctf_msg_iter_get_next_message@msg-iter.cpp:2715 [auto-disc-source-ctf-fs] Cannot handle state: msg-it-addr=0x613000000580, state=DSCOPE_EVENT_PAYLOAD_CONTINUE 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:63 Babeltrace 2 library postcondition not satisfied. 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:65 ------------------------------------------------------------------------ 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:66 Condition ID: `post:message-iterator-class-next-method:no-error-if-no-error-status`. 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:68 Function: bt_message_iterator_class_next_method(). 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:69 ------------------------------------------------------------------------ 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:70 Error is: 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:72 Current thread has an error, but user function returned a non-error status: status=OK 09-18 16:15:58.978 335803 335803 F LIB/ASSERT-COND bt_lib_assert_cond_failed@assert-cond.c:75 Aborting...
Files
Updated by Simon Marchi about 1 year ago
A bit more details: I think the trace was valid until I added the uint8_t timestamp; line in the event header. With that line added (and without adjusting the data stream), the data stream is too short, it ends in the middle of an event, and babeltrace doesn't seem to like it.
Updated by Simon Marchi about 1 year ago
Tentative patch: https://review.lttng.org/c/babeltrace/+/10902
Updated by Simon Marchi 6 months ago
This still fails with the ctf2 branch, but with a different error:
05-23 11:58:14.164 246275 246275 F LIB/ASSERT-COND bt_lib_assert_cond_failed@/home/smarchi/src/babeltrace/src/lib/assert-cond.c:66 Condition ID: `pre:message-packet-beginning-create-with-default-clock-snapshot:without-default-clock-snapshot`. 05-23 11:58:14.164 246275 246275 F LIB/ASSERT-COND bt_lib_assert_cond_failed@/home/smarchi/src/babeltrace/src/lib/assert-cond.c:68 Function: bt_message_packet_beginning_create_with_default_clock_snapshot(). 05-23 11:58:14.164 246275 246275 F LIB/ASSERT-COND bt_lib_assert_cond_failed@/home/smarchi/src/babeltrace/src/lib/assert-cond.c:69 ------------------------------------------------------------------------ 05-23 11:58:14.164 246275 246275 F LIB/ASSERT-COND bt_lib_assert_cond_failed@/home/smarchi/src/babeltrace/src/lib/assert-cond.c:70 Error is: 05-23 11:58:14.164 246275 246275 F LIB/ASSERT-COND bt_lib_assert_cond_failed@/home/smarchi/src/babeltrace/src/lib/assert-cond.c:72 Unexpected stream class configuration when creating a packet beginning or end message: no default clock snapshot is needed, but one was provided: stream-addr=0x50c00001cd80, stream-id=0, stream-name="/home/smarchi/Downloads/trace/channel0_0", stream-stream-class-addr=0x510000000c40, stream-stream-class-id=0, stream-trace-class-addr=0x508000002620, stream-trace-addr=0x50d0000017d0, stream-trace-name="", stream-packet-pool-size=0, stream-packet-pool-cap=0, sc-addr=0x510000000c40, sc-id=0, sc-is-frozen=1, sc-event-class-count=1, sc-packet-context-fc-addr=(nil), sc-event-common-context-fc-addr=(nil), sc-assigns-auto-ec-id=0, sc-assigns-auto-stream-id=0, sc-supports-packets=1, sc-packets-have-begin-default-cs=0, sc-packets-have-end-default-cs=0, sc-supports-discarded-events=0, sc-discarded-events-have-default-cs=0, sc-supports-discarded-packets=0, sc-discarded-packets-have-default-cs=0, sc-trace-class-addr=0x508000002620, sc-pcf-pool-size=0, sc-pcf-pool-cap=0, with-cs=1, cs-val=0
Actions