Bug#904456: clang-6.0: Stack traces displayed by sanitizers do not display debug symbols even though excecutable is built with them
Valentin
vakevk+debian at gmail.com
Tue Jul 24 14:58:10 BST 2018
Package: clang-6.0
Version: 1:6.0.1-2
Severity: normal
Dear Maintainer,
I am building a trivial executable (for example the first example from
http://clang.llvm.org/docs/MemorySanitizer.html) with -g
-fno-omit-frame-pointer and for examples -fsanitize=memory. When running
the executable the sanitizer correctly reports a problem with a stack
trace but the stack trace does not include funciton names and source
code line numbers (as seen in the previous link). This information
should be shown
I remember using the sanitizers about a month ago at which point I did
not encounter the problem.
I encountered a similar issue with the valgrind package which I could
fix by building valgrind from source. There is an open bug on the
valgrind package for this problem
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701480) in which a
user mentions that the problem is related to binutils.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages clang-6.0 depends on:
ii binutils 2.31.1-1
ii libc6 2.27-5
ii libc6-dev 2.27-5
ii libclang-common-6.0-dev 1:6.0.1-2
ii libclang1-6.0 1:6.0.1-2
ii libgcc-7-dev 7.3.0-25
ii libgcc1 1:8.1.0-10
ii libjsoncpp1 1.7.4-3
ii libllvm6.0 1:6.0.1-2
ii libobjc-7-dev 7.3.0-25
ii libstdc++-7-dev 7.3.0-25
ii libstdc++6 8.1.0-10
Versions of packages clang-6.0 recommends:
ii libomp-dev 6.0.1-1
ii llvm-6.0-dev 1:6.0.1-2
ii python 2.7.15-3
Versions of packages clang-6.0 suggests:
pn clang-6.0-doc <none>
pn gnustep <none>
pn gnustep-devel <none>
-- no debconf information
More information about the Pkg-llvm-team
mailing list