The "application has stopped unexpectedly" dialog shouldn't pop up when valgrind exits with SIGSEGV

[Martin]

One of the common use cases for valgrind is to run it no a program which is known to segfault, in order to figure out why the application segfaults. In those situations, valgrind will print its output and exit with a SIGSEGV. That part is expected.

However, when a system binary segfaults, Ubuntu will open a dialog with the message "Sorry, the application <application name> has stopped unexpectedly". That makes sense in most cases, but not for valgrind, because it's expected for valgrind to exit with SIGSEGV.

Attached is a screenshot of an expected segfault triggering the dialog.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: valgrind 1:3.17.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Apr 10 16:17:21 2021
InstallationDate: Installed on 2019-11-21 (505 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RebootRequiredPkgs:
 libc6
 libc6
SourcePackage: valgrind
UpgradeStatus: Upgraded to hirsute on 2021-03-16 (24 days ago)