Hi! On Thu, 2016-11-10 at 12:11:51 +0100, Andreas Beckmann wrote: > Package: dpkg > Version: 1.18.13 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + desktop-base
> during a test with piuparts I noticed a reproducible dpkg segfault > when installing desktop-base/experimental in a sid+experimental amd64 chroot. I cannot reproduce this, on a clean sid chroot by just installing desktop-base from experimental. :( > >From the attached log (scroll to the bottom...): > > Selecting previously unselected package desktop-base. > (Reading database ... 5376 files and directories currently installed.) > Preparing to unpack .../desktop-base_9.0.0~exp1_all.deb ... > Unpacking desktop-base (9.0.0~exp1) ... > Processing triggers for libglib2.0-0:amd64 (2.50.2-1) ... > No schema files found: doing nothing. > Setting up desktop-base (9.0.0~exp1) ... […] > dpkg: error processing package desktop-base (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > E: Sub-process /usr/bin/dpkg received a segmentation fault. This appears to be a problem with reportbroken_retexitstatus() in src/error.c when printing out the packages affected by the errors, so not something dangerous, but still annoying and wrong. From your backtrace it seems the function which has accumulated the package names cannot access those pointers anymore. And even though I cannot reproduce I think I know what's going on. The latest releases started freeing the memory pool when releaseing the database journal. Which means that this invalidates those stored references. I'll copy those strings for the next release so that we can still free the db. If you can still reproduce at will, I might like to provide a patch to make sure the fix works for you? If you could test this, probably later today, that'd be awesome! Thanks, Guillem