Package: valgrind Version: 1:3.15.0-1 Severity: normal It looks like valgrind doesn't support D programming language symbol mangling (as emitted by DMD, GDC or LDC2 compilers);
==29535== valgrind: Unrecognised instruction at address 0x1b38db. ==29535== at 0x1B38DB: _D3rcu__T3RCUTSQn1AZQl6updateMFNbPQuZv (rcu.d:390) ==29535== by 0x1B2F6F: _D3rcu6writerFZv (rcu.d:96) ==29535== by 0x1B3230: _D3rcu4mainFAAyaZ9__lambda3FZv (rcu.d:600) ==29535== by 0x1E52B7: _D4core6thread8osthread6Thread3runMFZv (in /home/user/vps1/home/baryluk/Projekty/rcu.d/rcu) ==29535== by 0x1FE929: thread_entryPoint (in /home/user/vps1/home/baryluk/Projekty/rcu.d/rcu) ==29535== by 0x487DF26: start_thread (pthread_create.c:479) ==29535== by 0x49AD31E: clone (clone.S:95) That is a bit unfortunate. Most of this compilers allow to emulate "C" mangling in debug symbols (ldc2 -gc), but it interferes with other things, and is not supported everywhere. gdb and objdump do demangle D symbols very well. I hope valgrind could pick it up too? -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (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.30-8 ii libc6-dbg 2.30-8 Versions of packages valgrind recommends: ii gdb 9.1-3 ii valgrind-dbg 1:3.15.0-1 Versions of packages valgrind suggests: pn alleyoop <none> ii kcachegrind 4:19.08.1-1+b1 pn valgrind-mpi <none> pn valkyrie <none> -- no debconf information
