Bug#1008309: clang-14: address sanitizer creates broken binaries
Sylvestre Ledru
sylvestre at debian.org
Tue Apr 19 21:14:26 BST 2022
Also, please provide a test case. it isn't easy for us to test with big
software!
Cheers
S
Le 26/03/2022 à 17:05, Christian Göttsche a écrit :
> Package: clang-14
> Version: 1:14.0.0-1
> Severity: grave
>
> Using address sanitizer with Clang 14 produces broken binaries while
> using Clang 13 works fine, e.g for SELint:
>
> git clone https://github.com/TresysTechnology/selint
> cd selint/
> ./autogen.sh
> ./configure CC=clang-14 CFLAGS='-O1 -g -fsanitize=address
> -fsanitize-address-use-after-scope -fno-omit-frame-pointer'
> make check
>
> results in
>
> PASS: check_maps
> ../test-driver: line 112: 17567 Segmentation fault (core
> dumped) "$@" >> "$log_file" 2>&1
> FAIL: check_tree
> PASS: check_parsing
> PASS: check_parse_functions
> PASS: check_parse_fc
> PASS: check_template
> PASS: check_check_hooks
> PASS: check_fc_checks
> ../test-driver: line 112: 17672 Segmentation fault (core
> dumped) "$@" >> "$log_file" 2>&1
> FAIL: check_file_list
> PASS: check_if_checks
> PASS: check_runner
> ../test-driver: line 112: 17727 Segmentation fault (core
> dumped) "$@" >> "$log_file" 2>&1
> FAIL: check_selint_config
> PASS: check_te_checks
> ../test-driver: line 112: 17764 Segmentation fault (core
> dumped) "$@" >> "$log_file" 2>&1
> FAIL: check_string_list
> PASS: check_perm_macro
> ../test-driver: line 112: 17780 Segmentation fault (core
> dumped) "$@" >> "$log_file" 2>&1
> FAIL: check_startup
> ../test-driver: line 112: 17808 Segmentation fault (core
> dumped) "$@" >> "$log_file" 2>&1
> FAIL: check_ordering
>
> with crashes like
>
> PID: 17968 (check_selint_co)
> UID: 1000 (christian)
> GID: 1000 (christian)
> Signal: 11 (SEGV)
> Timestamp: Sat 2022-03-26 16:53:06 CET (9min ago)
> Command Line: ./tests/check_selint_config
> Executable: ./selint/tests/check_selint_config
> Control Group: /user.slice/user-1000.slice/user at 1000.service/app.slice/app-org.kde.konsole-e43b2d75763e4b0da70e80f64c26a3e4.scope
> Unit: user at 1000.service
> User Unit: app-org.kde.konsole-e43b2d75763e4b0da70e80f64c26a3e4.scope
> Slice: user-1000.slice
> Owner UID: 1000 (christian)
> Boot ID: 10c66335d13d4d1eadcfd8c0158aa69e
> Machine ID: 9c96f8739cf9458d85028070c30b63fc
> Hostname: debianHome
> Storage: /var/lib/systemd/coredump/core.check_selint_co.1000.10c66335d13d4d1eadcfd8c0158aa69e.17968.1648309986000000.zst
> (present)
> Disk Size: 129.0K
> Message: Process 17968 (check_selint_co) of user 1000 dumped core.
>
> Module /usr/lib/x86_64-linux-gnu/libc.so.6 with
> build-id dbe01d361066dd24f54239c184702d6e515d3134
> Module /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
> with build-id 41994ebf17dd9d27781e6aa7d5d380760bfc938c
> Module linux-vdso.so.1 with build-id
> c556e37440595bd7e11951e409de7d941439a8ef
> Stack trace of thread 17968:
> #0 0x0000606ade2de9e0 n/a (n/a + 0x0)
> ELF object binary architecture: AMD x86-64
>
> and a backtrace of
>
> #0 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #1 <signal handler called>
> No symbol table info available.
> #2 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #3 <signal handler called>
> No symbol table info available.
> #4 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #5 <signal handler called>
> No symbol table info available.
> #6 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #7 <signal handler called>
> No symbol table info available.
> #8 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #9 <signal handler called>
> No symbol table info available.
> #10 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #11 <signal handler called>
> No symbol table info available.
> #12 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #13 <signal handler called>
> No symbol table info available.
> #14 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #15 <signal handler called>
> No symbol table info available.
> #16 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #17 <signal handler called>
> No symbol table info available.
> #18 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #19 <signal handler called>
> No symbol table info available.
> #20 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #21 <signal handler called>
> No symbol table info available.
> #22 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #23 <signal handler called>
> No symbol table info available.
> #24 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #25 <signal handler called>
> No symbol table info available.
> #26 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #27 <signal handler called>
> No symbol table info available.
> #28 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #29 <signal handler called>
> No symbol table info available.
> #30 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #31 <signal handler called>
> No symbol table info available.
> #32 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #33 <signal handler called>
> No symbol table info available.
> #34 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #35 <signal handler called>
> No symbol table info available.
> #36 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #37 <signal handler called>
> No symbol table info available.
> #38 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #39 <signal handler called>
> No symbol table info available.
> #40 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #41 <signal handler called>
> No symbol table info available.
> #42 0x0000606ade2de9e0 in ?? ()
> No symbol table info available.
> #43 <signal handler called>
> No symbol table info available.
> #44 0x0000606ade2f4591 in ?? ()
> No symbol table info available.
> #45 0x0000040000002000 in ?? ()
> No symbol table info available.
> #46 0x0000000000000000 in ?? ()
> No symbol table info available.
>
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages clang-14 depends on:
> ii binutils 2.38-3
> ii libc6 2.34-0experimental3
> ii libc6-dev 2.34-0experimental3
> ii libclang-common-14-dev 1:14.0.0-1
> ii libclang-cpp14 1:14.0.0-1
> ii libclang1-14 1:14.0.0-1
> ii libgcc-11-dev 11.2.0-19
> ii libgcc-s1 12-20220319-1
> ii libllvm14 1:14.0.0-1
> ii libobjc-11-dev 11.2.0-19
> ii libstdc++-11-dev 11.2.0-19
> ii libstdc++6 12-20220319-1
> ii llvm-14-linker-tools 1:14.0.0-1
>
> Versions of packages clang-14 recommends:
> ii llvm-14-dev 1:14.0.0-1
> ii python3 3.9.8-1
>
> Versions of packages clang-14 suggests:
> pn clang-14-doc <none>
>
> -- no debconf information
>
> _______________________________________________
> Pkg-llvm-team mailing list
> Pkg-llvm-team at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team
More information about the Pkg-llvm-team
mailing list