Public bug reported:
* See upstream bug report with reproducer: https://bugs.lttng.org/issues/1439
* See upstream bufix: https://review.lttng.org/c/babeltrace/+/17654
babeltrace 1.5 itself hasn't changed in a while, at least not since
Noble. However, its Python bindings are built with SWIG 4.3.0 on
Resolute vs SWIG 4.2.0 on Noble. A change in SWIG results in a segfault
in the babeltrace Python bindings. See the full explanation in the
upstream bugfix commit message.
The fix above is somewhat simple. Could this be patched in Resolute?
** Affects: babeltrace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2152060
Title:
Python bindings segfault when reading trace if built with SWIG >=4.3.0
(e.g., Resolute)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/babeltrace/+bug/2152060/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
