Bug#1108192: dpkg: segfault in dpkg-trigger

Guillem Jover <[email protected]>
Newsgroups gmane.linux.debian.devel.dpkg.bugs
Message-ID <aFh4HdHG_JOHQrQt__37155.437939667$1750628489$gmane$org@thunder.hadrons.org>
Control: tag -1 unreproducible moreinfo

Hi!

On Sun, 2025-06-22 at 14:38:40 -0400, Noah Meyerhans wrote:
> Package: dpkg
> Version: 1.22.20
> Severity: normal

> This may be a usage error on my part, but it should probably not be
> segfaulting either way.  While investigating a possible solution to
> #1108166, I encountered the following segfault in dpkg-trigger:
> 
> root@satest-trixie:~# dpkg-trigger --by-package=sa-compile --no-await --no-act sa-compile-upgrade
> [  721.686463] dpkg-trigger[5137]: segfault at c0 ip 00007f8b7d127d8a sp 00007fffe1a0dc90 error 4 in libc.so.6[64d8a,7f8b7d0e
> b000+165000] likely on CPU 0 (core 0, socket 0)
> [  721.688762] Code: 00 e8 ea 3d 02 00 48 89 f9 e9 a5 fa ff ff 66 90 41 57 41 56 41 55 41 54 49 89 d4 55 48 89 f5 53 48 89 fb
>  48 81 ec f8 00 00 00 <8b> 87 c0 00 00 00 64 4c 8b 2c 25 28 00 00 00 4c 89 ac 24 e8 00 00
> Segmentation fault

I tried that invocation on a minimal sid chroot, with the sa-compile
package installed, and I could not reproduce the segfault. If you can
still reproduce that, could you send at least the dpkg status file and
the /var/lib/dpkg/triggers/ directory? If that contains sensitive data,
feel free to send it privately to me.

Also if you could also send a backtrace that would be great.

Thanks,
Guillem
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.