Babeltrace - 2.1 open 0% 7 issues (0 closed — 7 open) Related issues Bug #1227: cli: Error when using --clock-cycles and -c sink.text.pretty at the same time Actions Bug #1229: flt.utils.trimmer: with no date, beginning time cannot be greater than end time Actions Bug #1230: flt.utils.trimmer: local time can be nonexistent or ambiguous with DST Actions Bug #1232: src.ctf.fs: variant option names without their tag equivalent are accepted, but the decoding process asserts Actions Bug #1235: configure.ac: using python-config --libs instead of python-config --ldflags Actions Bug #1237: Built-in plugins are not relinked to the application after a modification Actions Feature #1233: Python: Add __str__ to Message types, and perhaps other types Actions
Babeltrace - stable 2.0 open 18% 16 issues (3 closed — 13 open) Related issues Bug #1221: Babeltrace 2 sometimes fail on live trace with lttng-clear feature Actions Bug #1222: src.ctf.lttng-live: reading two per-pid traces does not emit messages Actions Bug #1223: Check for cmp and diff in configure Actions Bug #1224: Crash while reading a live per-pid trace Actions Bug #1225: src.ctf.lttng-live: `sessions` query error reporting Actions Bug #1228: calling seek to beginning after seek to ns from origin Actions Bug #1231: AddressSanitizer detects an global buffer overflow when we iterate over plugin .so descriptors Actions Bug #1234: src.text.dmesg: some kernel ring buffer lines can be wrongly sorted by time, leading to a muxer error Actions Bug #1236: SIGTRAP in glib found during fuzzing Actions Bug #1240: Can't write plugins solely with `--enable-python-plugins` Actions Bug #1254: Trace with non-monotonic clocks make babeltrace2 abort Actions Bug #1255: Babeltrace2 fails to process trace with begin timestamp of second packet smaller than begin timestamp of first packet Actions Bug #1258: Segmentation fault when running with --debug Actions Bug #1259: improved to description/usecases for streams and packets. Actions Bug #1260: Babeltrace 2 refuses a trace when a previous packet has an end time > begin of the next packet Actions Feature #1226: Allow making graph execution more "event-based" Actions