Dear Maintainer,
this SIGSEGV and also the valgrind "invalid read"
below ledger::journal_t::clear_xdata can also be
seen in a Debian 11 Bullseye VM.
Because valgrind points already to a use-after-free,
and the output "Done." is printed,
might the issue here be, that python does destruct the
"sess
Dnia Fri, Nov 18, 2022 at 02:45:12PM -0400, David Bremner napisał(a):
> Did you try python3-ledger-dbgsym? You need to enable the debian-debug
> archive [1]
>
> [1]: https://wiki.debian.org/HowToGetABacktrace
Right, thanks for reminding me!
Here is a possibly more useful backtrace, then:
(gdb)
Marcin Owsiany writes:
> Package: python3-ledger
> Version: 3.2.1-8+b5
> Severity: normal
>
> Dear Maintainer,
>
> Here is a short repro script, that generates a segmentation violation on
> completion. I include a backtrace from GDB, but unfortunately I could not find
> debugging symbols for the
Package: python3-ledger
Version: 3.2.1-8+b5
Severity: normal
Dear Maintainer,
Here is a short repro script, that generates a segmentation violation on
completion. I include a backtrace from GDB, but unfortunately I could not find
debugging symbols for the ledger extension nor libboost-python.
po
4 matches
Mail list logo
