Bug#1144219: glycin-loaders: with valgrind, "Loader process exited early with status '1'"

Simon McVittie smcv at debian.org
Wed Aug 12 18:32:18 BST 2026


On Wed, 12 Aug 2026 at 16:23:45 +0200, Vincent Lefevre wrote:
>--417228-- WARNING: unhandled amd64-linux syscall: 317

According to my /usr/include/x86_64-linux-gnu/asm/unistd_64.h, this is 
seccomp(). It doesn't really surprise me if glycin, a framework for 
confining potentially attackable image decoders into a sandboxed 
subprocess, doesn't work in the case where it's unable to apply seccomp 
confinement to the sandbox.

After glycin has been updated to a newer upstream release, it'll be 
possible to use environment variable 
GLYCIN_DISABLE_SANDBOX=i-know-the-risks while valgrinding, and that 
would probably bypass this, although I realise that doesn't help you 
immediately.

     smcv



More information about the pkg-gnome-maintainers mailing list