Created attachment 642774 [details] emerge --info Rebuilt most of system with emerge --emptytree --keep-going=y @world recently, noticed problems with lilv commands (eg. lv2ls, lilv-bench) which segfault when run. The coredump backtrace points to sord: Core was generated by `lv2ls'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f0bb3dc78c8 in sord_free (model=0x55bb147c8650) at ../src/zix/btree.c:664 664 return frame->node->vals[frame->index]; (gdb) bt #0 0x00007f0bb3dc78c8 in sord_free (model=0x55bb147c8650) at ../src/zix/btree.c:664 #1 0x00007f0bb3fc526c in lilv_world_free (world=0x55bb147c82a0) at ../src/world.c:175 #2 0x000055bb133a92ab in main (argc=<optimized out>, argv=<optimized out>) at ../utils/lv2ls.c:91 If dev-libs/sord is re-emerged with gcc-9.3.0 this doesn't happen.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c47e948b711401b0d2dcab6e21f3a9874302e255 commit c47e948b711401b0d2dcab6e21f3a9874302e255 Author: Miroslav Šulc <fordfrog@gentoo.org> AuthorDate: 2020-09-05 17:16:28 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2020-09-05 17:16:43 +0000 dev-libs/sord: fixed compilation with gcc10 + added live Closes: https://bugs.gentoo.org/726312 Package-Manager: Portage-3.0.5, Repoman-3.0.1 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> dev-libs/sord/files/sord-0.16.4-gcc10.patch | 25 ++++++++++ .../{sord-0.16.4.ebuild => sord-0.16.4-r1.ebuild} | 4 ++ dev-libs/sord/sord-9999.ebuild | 57 ++++++++++++++++++++++ 3 files changed, 86 insertions(+)
