Package: valgrind Version: 1:3.15.0-1 Severity: normal Dear Maintainer,
Running the following command: $ valgrind --vgdb-stop-at=all nautilus gives me: ==99780== Memcheck, a memory error detector ==99780== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==99780== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==99780== Command: nautilus ==99780== ==99780== (action at startup) vgdb me ... ==99780== ==99780== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==99780== /path/to/gdb nautilus ==99780== and then give GDB the following command ==99780== target remote | /usr/lib/x86_64-linux-gnu/valgrind/../../bin/vgdb --pid=99780 ==99780== --pid is optional if only one valgrind process is running ==99780== However the comamnd that this output suggests to give to GDB is incorrect: vgdb lives at /usr/bin/vgdb, not where the output suggests. Thanks for your maintainership of valgrind in Debian! Andreas -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-rc3 (SMP w/8 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages valgrind depends on: ii libc6 2.29-2 ii libc6-dbg 2.29-2 Versions of packages valgrind recommends: ii gdb 8.3.1-1 ii valgrind-dbg 1:3.15.0-1 Versions of packages valgrind suggests: pn alleyoop <none> pn kcachegrind <none> pn valgrind-mpi <none> pn valkyrie <none> -- no debconf information
