Your message dated Thu, 04 Jul 2024 12:34:31 +0000
with message-id <e1splft-001j5u...@fasolo.debian.org>
and subject line Bug#1067005: fixed in llvm-toolchain-18 1:18.1.8-2~exp1
has caused the Debian Bug report #1067005,
regarding libLLVM.so symbols are no longer versioned?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libllvm18
Version: 1:18.1.1-1
Severity: serious
File: /usr/lib/llvm-18/lib/libLLVM.so.18.1, 
/usr/lib/x86_64-linux-gnu/libLLVM-17.so.1
X-Debbugs-Cc: Sylvestre Ledru <sylves...@debian.org>, Gianfranco Costamagna 
<costamagnagianfra...@yahoo.it>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I'm having a bit of a deja-vu here, because this exact kind of bug was
happening a while ago and was fixed, but looks like it's back?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846410
(same bugs happened in other distros too)

(TLDR: when two different libLLVM versions happen to [transitively] exist
within one running process, you may get weird segfaults.)

Could you please double-check that the symbols for the `libLLVM.so.18.1`
and `libLLVM-17.so.1` are versioned? If they are not, this bugs' severity
is actually Grave (and affecting at least LLVM17 too?)

Concretely, i'm hitting it when building halide package and then trying to
run it's tests with mesa's RustiCL implementation, llvmpipe driver.
To reproduce, `gbp buildpackage` on
https://salsa.debian.org/LebedevRI-guest/halide/-/commits/debian-opencl-FOR-BUGREPORT

Weirdly-enough, it happens when building the package,
but does not happen with manually hand-built halide.
```
$ export Halide_TARGET=host-opencl
$ export OCL_ICD_VENDORS=rusticl.icd
$ export RUSTICL_ENABLE=llvmpipe
$ gdb 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions
 -ex 'run' -ex 'thread apply all bt full'
GNU gdb (Debian 13.2-1+b1) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions...
Starting program: 
/build/halide-17.0.1-build/build/stage-2/halide/test/correctness/correctness_boundary_conditions
 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdce006c0 (LWP 172580)]
[New Thread 0x7fffdc4006c0 (LWP 172581)]
[New Thread 0x7fffdba006c0 (LWP 172582)]
[New Thread 0x7fffdb0006c0 (LWP 172583)]
[New Thread 0x7fffda6006c0 (LWP 172584)]
[New Thread 0x7fffd9c006c0 (LWP 172585)]
[New Thread 0x7fffd92006c0 (LWP 172586)]
[New Thread 0x7fffd3e006c0 (LWP 172587)]
[New Thread 0x7fffd34006c0 (LWP 172588)]
[New Thread 0x7fffd2a006c0 (LWP 172589)]
[New Thread 0x7fffd20006c0 (LWP 172590)]
[New Thread 0x7fffd16006c0 (LWP 172591)]
[New Thread 0x7fffd0c006c0 (LWP 172592)]
[New Thread 0x7fffc7e006c0 (LWP 172593)]
[New Thread 0x7fffc74006c0 (LWP 172594)]
[New Thread 0x7fffc6a006c0 (LWP 172595)]
[New Thread 0x7fffc60006c0 (LWP 172596)]
[New Thread 0x7fffc56006c0 (LWP 172597)]
[New Thread 0x7fffc4c006c0 (LWP 172598)]
[New Thread 0x7fffbbe006c0 (LWP 172599)]
[New Thread 0x7fffbb4006c0 (LWP 172600)]
[New Thread 0x7fffbaa006c0 (LWP 172601)]
[New Thread 0x7fffba0006c0 (LWP 172602)]
[New Thread 0x7fffb96006c0 (LWP 172603)]
[New Thread 0x7fffb8c006c0 (LWP 172604)]
[New Thread 0x7fffafe006c0 (LWP 172605)]
[New Thread 0x7fffaf4006c0 (LWP 172606)]
[New Thread 0x7fffaea006c0 (LWP 172607)]
[New Thread 0x7fffae0006c0 (LWP 172608)]
[New Thread 0x7fffad6006c0 (LWP 172609)]
[New Thread 0x7fffacc006c0 (LWP 172610)]
[New Thread 0x7fffa3e006c0 (LWP 172611)]
[New Thread 0x7fffa34006c0 (LWP 172612)]
[New Thread 0x7fffa2a006c0 (LWP 172613)]
[New Thread 0x7fffa20006c0 (LWP 172614)]
[New Thread 0x7fffa16006c0 (LWP 172615)]
[New Thread 0x7fffa0c006c0 (LWP 172616)]
[New Thread 0x7fff97e006c0 (LWP 172617)]
[New Thread 0x7fff974006c0 (LWP 172618)]
[New Thread 0x7fff96a006c0 (LWP 172619)]
[New Thread 0x7fff960006c0 (LWP 172620)]
[New Thread 0x7fff956006c0 (LWP 172621)]
[New Thread 0x7fff94c006c0 (LWP 172622)]
[New Thread 0x7fff8be006c0 (LWP 172623)]
[New Thread 0x7fff8b4006c0 (LWP 172624)]
[New Thread 0x7fff8aa006c0 (LWP 172625)]
[New Thread 0x7fff8a0006c0 (LWP 172626)]
[New Thread 0x7fff896006c0 (LWP 172627)]
[New Thread 0x7fff88c006c0 (LWP 172628)]
[New Thread 0x7fff7fe006c0 (LWP 172629)]
[New Thread 0x7fff7f4006c0 (LWP 172630)]
[New Thread 0x7fff7ea006c0 (LWP 172631)]
[New Thread 0x7fff7e0006c0 (LWP 172632)]
[New Thread 0x7fff7d6006c0 (LWP 172633)]
[New Thread 0x7fff7cc006c0 (LWP 172634)]
[New Thread 0x7fff73e006c0 (LWP 172635)]
[New Thread 0x7fff734006c0 (LWP 172636)]
[New Thread 0x7fff72a006c0 (LWP 172637)]
[New Thread 0x7fff720006c0 (LWP 172638)]
[New Thread 0x7fff716006c0 (LWP 172639)]
[New Thread 0x7fff70c006c0 (LWP 172640)]
[New Thread 0x7fff67e006c0 (LWP 172641)]
[New Thread 0x7fff674006c0 (LWP 172642)]
[New Thread 0x7fff66a006c0 (LWP 172643)]
[New Thread 0x7fffd88006c0 (LWP 172645)]

Thread 1 "correctness_bou" received signal SIGSEGV, Segmentation fault.
0x00007fffef1a6160 in 
llvm::AnalysisManager<llvm::Module>::getResultImpl(llvm::AnalysisKey*, 
llvm::Module&) () from /usr/lib/llvm-18/lib/libLLVM.so.18.1

<...>

Thread 1 (Thread 0x7fffea839280 (LWP 172577) "correctness_bou"):
#0  0x00007fffef1a6160 in 
llvm::AnalysisManager<llvm::Module>::getResultImpl(llvm::AnalysisKey*, 
llvm::Module&) () from /usr/lib/llvm-18/lib/libLLVM.so.18.1
No symbol table info available.
#1  0x00007fffef1a6077 in 
llvm::AnalysisManager<llvm::Module>::getResultImpl(llvm::AnalysisKey*, 
llvm::Module&) () from /usr/lib/llvm-18/lib/libLLVM.so.18.1
No symbol table info available.
#2  0x00007fffef1d0a1d in llvm::VerifierPass::run(llvm::Module&, 
llvm::AnalysisManager<llvm::Module>&) () from 
/usr/lib/llvm-18/lib/libLLVM.so.18.1
No symbol table info available.
#3  0x00007ffff0659681 in ?? () from /usr/lib/llvm-18/lib/libLLVM.so.18.1
No symbol table info available.
#4  0x00007fffe1d2e264 in llvm::PassManager<llvm::Module, 
llvm::AnalysisManager<llvm::Module>>::run(llvm::Module&, 
llvm::AnalysisManager<llvm::Module>&) () from 
/lib/x86_64-linux-gnu/libLLVM-17.so.1
No symbol table info available.
#5  0x00007fffdecb10e4 in ?? () from /lib/x86_64-linux-gnu/libclang-cpp.so.17
No symbol table info available.
#6  0x00007fffdecaa082 in clang::EmitBackendOutput(clang::DiagnosticsEngine&, 
clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, 
clang::TargetOptions const&, clang::LangOptions const&, llvm::StringRef, 
llvm::Module*, clang::BackendAction, 
llvm::IntrusiveRefCntPtr<llvm::vfs::FileSystem>, 
std::unique_ptr<llvm::raw_pwrite_stream, 
std::default_delete<llvm::raw_pwrite_stream> >) () from 
/lib/x86_64-linux-gnu/libclang-cpp.so.17
No symbol table info available.
#7  0x00007fffdf039e9e in ?? () from /lib/x86_64-linux-gnu/libclang-cpp.so.17
No symbol table info available.
#8  0x00007fffddce58e6 in clang::ParseAST(clang::Sema&, bool, bool) () from 
/lib/x86_64-linux-gnu/libclang-cpp.so.17
No symbol table info available.
#9  0x00007fffdfa2f949 in clang::FrontendAction::Execute() () from 
/lib/x86_64-linux-gnu/libclang-cpp.so.17
No symbol table info available.
#10 0x00007fffdf9a9364 in 
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) () from 
/lib/x86_64-linux-gnu/libclang-cpp.so.17
No symbol table info available.
#11 0x00007fffe8e915f3 in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#12 0x00007fffe8e9330e in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#13 0x00007fffe8e8790d in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#14 0x00007fffe88015a1 in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#15 0x00007fffe875fc7b in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#16 0x00007fffe875ef02 in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#17 0x00007fffe8722dcc in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#18 0x00007fffe8722a49 in ?? () from /lib/x86_64-linux-gnu/libRusticlOpenCL.so.1
No symbol table info available.
#19 0x00007fffea81beb7 in ?? ()
No symbol table info available.
#20 0x0100000000000000 in ?? ()
No symbol table info available.
#21 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb) A debugging session is active.

        Inferior 1 [process 172577] will be killed.

Quit anyway? (y or n) [answered Y; input not from terminal]
make[4]: Leaving directory '/build/halide-17.0.1'

```

Roman.


- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.9-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libllvm18:amd64 depends on:
ii  libc6       2.37-15.1
ii  libedit2    3.1-20230828-1
ii  libffi8     3.4.6-1
ii  libgcc-s1   14-20240303-1
ii  libstdc++6  14-20240303-1
ii  libtinfo6   6.4+20240113-1
ii  libxml2     2.9.14+dfsg-1.3+b2
ii  libz3-4     4.8.12-3.1+b2
ii  libzstd1    1.5.5+dfsg2-2
ii  zlib1g      1:1.3.dfsg-3.1

libllvm18:amd64 recommends no packages.

libllvm18:amd64 suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE+UikBxeiu50LOdFYgbqkFMWfZdAFAmX16bkACgkQgbqkFMWf
ZdCyug//auWBEcbChrJdlYCabf6upvF5vtVrRTx00xzA5GPbSJ725m3y3pDFH01a
c0Pt7AyxIZq8jRuzYeKQe8y2M6z/cAMN6RxvMKz35c/mwRDCmPWlOthvsHzKuZF0
hCwe+ADBE7KjkA9xSyHMJ+081Quh6+SiVvmrb+3hks4FNq6gp5Vv18kW8EHDCYoH
H4+407Pxx+GzqOTDt/KApTPtsApZIzPu1+jy4SyVoTwmoaM2KIEUMGe0AmCV7vMT
r8f6QijQx5ldtQSV1QO02abfjBrNLqLw/OeU6PQZz7qOr1+i6jo4doLKPW9IwHUP
XO7hduMFU5zzn6CoUOy/yolGyqxB/YWjB2UItpEDZDfDAU4a1+yDWD3W2zSI152V
4IluJb/9KJkXjfbtv53m+Pv51YKXhmAUIjAsHMgJS5KHxNl0DNsKUt+Fl7YiC4Zc
0FtLsZcdtqjrADhsKe8vWKu/rjt/PMLmMqRIcntvkr/GG8u5gbq48MRNedRN/P+S
oUYnQsB3CQ3/bUQZAQhIigXeXdzCb4fU5Swe2KS0JcSPNWJpgbzXk42y9bxPoYB7
CRhkzqnxe24MiA1A0dQclH0wc+EVftVnfrNVU4p2GSobjlVpYv+onrYBKDptSZ3o
P+jTOi6igVznYX75tUhy1ZsKxVsM43KX/92HXSQQu0naBGi+hWQ=
=9Akx
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-18
Source-Version: 1:18.1.8-2~exp1
Done: Sylvestre Ledru <sylves...@debian.org>

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-18, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru <sylves...@debian.org> (supplier of updated llvm-toolchain-18 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 01 Jul 2024 22:27:25 +0200
Source: llvm-toolchain-18
Architecture: source
Version: 1:18.1.8-2~exp1
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-t...@lists.alioth.debian.org>
Changed-By: Sylvestre Ledru <sylves...@debian.org>
Closes: 1067005 1067699 1073201
Changes:
 llvm-toolchain-18 (1:18.1.8-2~exp1) experimental; urgency=medium
 .
   [ Sylvestre Ledru ]
   * Enable LLVM_ENABLE_PER_TARGET_RUNTIME_DIR
     to move the libraries into multi archi directories
   * Bring back libLLVM to be installed in /usr/lib/llvm-18/lib/libLLVM-18.so
     instead of /usr/lib/llvm-18/lib/libLLVM.so
     Same for libclang (remove usr/lib/llvm-18/lib/libclang.so.1
     This should make the packages multiarch co installable again
     (Closes: #1067699, #1067005)
     (LP: #2063207)
   * Introduce the new variable @DEB_HOST_MULTIARCH_LLVM@ in the build system
     because the LLVM triple is different than Debian
     x86_64-pc-linux-gnu instead of x86_64-linux-gnu
   * autopkgtest: only run libllvmlibc test on supported archs
 .
   [ John Paul Adrian Glaubitz ]
   * Don't install Gold plugin on sparc64
   * Disable LLVM testsuite on x32
   * Install liborc_rt-x86_64.a on x32
   * Install hwasan_symbolize on x32
 .
   [ Norbert Lange ]
   * build lldb with Intel PT support on x86, amd64
 .
   [ Aurelien Jarno ]
   * Enable lldb on riscv64.
 .
   [ Zixing Liu <zixing....@canonical.com> ]
   * d/p/clang-record-gcc-switches-by-default.patch: add a patch to force clang
     record gcc switches by default
 .
   [ Gianfranco Costamagna ]
   * Rename check-libcxxabi in check-cxxabi.
   * Rename check-libcxx in check-cxx
   * Drop removed check-sanitizer (Closes: #1073201)
Checksums-Sha1:
 323e1c9e543e1a5f3fc5bd3738a99ab2a1fd955b 8365 
llvm-toolchain-18_18.1.8-2~exp1.dsc
 fc8c3966a1f67f1a4f121811acc0a60ed63dc72b 164564 
llvm-toolchain-18_18.1.8-2~exp1.debian.tar.xz
 609ccbf779c5cef88fbfef97c9c78dad433ab4f9 37762 
llvm-toolchain-18_18.1.8-2~exp1_amd64.buildinfo
Checksums-Sha256:
 4127a85f636569e33cd5664c725828fbb1a64c3eb9f2da3efcadde53102566b6 8365 
llvm-toolchain-18_18.1.8-2~exp1.dsc
 9dad80904021220ece02e17adcf8e603f1ab662f5b93fe2d05979d58aca305a7 164564 
llvm-toolchain-18_18.1.8-2~exp1.debian.tar.xz
 f646524012d4c7644fe90505c609f9319463b8bd59fdaa3704c1924a55fe7c09 37762 
llvm-toolchain-18_18.1.8-2~exp1_amd64.buildinfo
Files:
 0dc1b3f34324fbeb6537884321e4fa35 8365 devel optional 
llvm-toolchain-18_18.1.8-2~exp1.dsc
 fda1e774d7a770ad0b8bbb30c8b29510 164564 devel optional 
llvm-toolchain-18_18.1.8-2~exp1.debian.tar.xz
 f5b9795c0a45549c7b780ca6836aebc6 37762 devel optional 
llvm-toolchain-18_18.1.8-2~exp1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmaGjfsACgkQfmUo2nUv
G+HDkhAAkZNjFUiL+BQdF8YDx4V+vsqe66GDwYl7TkrSLJvYzSboV9URb2pjUEDU
3EWIie+VTSSmNt/PcmNDIF94LQGdf7w5rG8QV+zrEpCM2J6dQpPrTBSk0wE/arHY
BzrqgoAjumKIpj13Ot736a8d4xjqARF0V094UgVd/pgzmkS4AEnNbCVYPKPN1A1/
OUSVynmJgLaoGLRKMO2VbxY7bIPqGnSaf4tAn/5iXkgIXjnZGTIqzoBOkWnRgAlc
sDgWZ4gKAc8J9ebc6ReA0n47x7x/dbsh7lSS+hSAFOGreL7N23KvR8qtnXhNadI2
hR2fUrMLt6DgOwdNmFJId65N1wo7GTzbtfrA0Bm4lOsshiLkFGKhTS9NfXuRc4gW
SReTbmAXNUsUfdqo7lFiGMtWX7XM3ArTbTjqzdo4tDerRxpJM9y0QPzIH/CRVvjv
57wjGNWQO4IaCFo9l7huVq/wbqJb1ZTo/+FdOVnO5gfyy2+/z77vdBa/uUYsNMqm
GTm8/Arb6KqqeWAQazfDC0XLeIfnP5FuNZ4NKRST1fcdBgPmYgiMN3sGEBg1KTXF
JC1L12uYwvrNm1TA6OBw9A5DXKj21qVh44+Etwug0a4ySVI3R0bJvutlRBecWku/
EEThqipwKT/VQRpQmllIWU14+vHqv6dBuIsKQMWjm74pxevGo4Q=
=ABDZ
-----END PGP SIGNATURE-----

Attachment: pgp7w6HkF2Q6n.pgp
Description: PGP signature


--- End Message ---

Reply via email to