Your message dated Thu, 07 Feb 2019 03:13:19 +0000 with message-id <E1gra7r-000G9u-7I@fasolo.debian.org> and subject line Bug#920171: Removed package(s) from unstable has caused the Debian Bug report #836848, regarding libasan3: AddressSanitizer breaks when LD_PRELOAD is defined 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 owner@bugs.debian.org immediately.) -- 836848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836848 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libasan3: AddressSanitizer breaks when LD_PRELOAD is defined
- From: Vincent Lefevre <vincent@vinc17.net>
- Date: Tue, 6 Sep 2016 16:36:55 +0200
- Message-id: <20160906143655.GA24866@cventin.lip.ens-lyon.fr>
Package: libasan3 Version: 6.2.0-3 Severity: normal When LD_PRELOAD is defined (which can be a consequence of gtk3-nocsd being installed and the user being in an X11 session), I get: cventin:~> gcc -fsanitize=address t.c cventin:~> ./a.out ==22051==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD. Something should be done. This was very confusing at first, because the problem first came here when I ran a configure script which was working a few days ago (after investigation, it is now clear that the reason was that it wasn't under a X11 session a few days ago), and just saw: checking whether we are cross compiling... configure: error: in `/home/vlefevre/tmp/mpfr-old': configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details I could see the error message, but the reason wasn't clear yet (I initially thought of a regression after a recent upgrade). So, I think that if possible, having LD_PRELOAD already set shouldn't affect ASan. Shouldn't -static-libasan be the default, for instance? If this is not possible, various things should be clarified: 1. The error message should be more informative, e.g. when LD_PRELOAD is set, say that LD_PRELOAD is set but ASan runtime does not appear in LD_PRELOAD or does not come first. 2. The gcc(1) man page does not mention LD_PRELOAD at all. Ditto for the GCC manual. 3. How to find the right ASan runtime *automatically* should also be documented. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libasan3 depends on: ii gcc-6-base 6.2.0-3 ii libc6 2.24-2 ii libgcc1 1:6.2.0-3 ii libstdc++6 6.2.0-3 libasan3 recommends no packages. libasan3 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 539912-done@bugs.debian.org,666106-done@bugs.debian.org,773065-done@bugs.debian.org,781457-done@bugs.debian.org,798710-done@bugs.debian.org,814221-done@bugs.debian.org,823778-done@bugs.debian.org,827787-done@bugs.debian.org,829604-done@bugs.debian.org,833850-done@bugs.debian.org,833931-done@bugs.debian.org,836848-done@bugs.debian.org,836864-done@bugs.debian.org,836944-done@bugs.debian.org,838874-done@bugs.debian.org,840190-done@bugs.debian.org,841220-done@bugs.debian.org,841419-done@bugs.debian.org,841533-done@bugs.debian.org,843198-done@bugs.debian.org,844439-done@bugs.debian.org,845493-done@bugs.debian.org,846148-done@bugs.debian.org,846214-done@bugs.debian.org,846530-done@bugs.debian.org,850841-done@bugs.debian.org,853287-done@bugs.debian.org,856274-done@bugs.debian.org,858890-done@bugs.debian.org,859116-done@bugs.debian.org,860823-done@bugs.debian.org,862113-done@bugs.debian.org,863820-done@bugs.debian.org,865115-done@bugs.debian.org,868449-done@bugs.debian.org,873662-done@bu gs.debian.org,873691-done@bugs.debian.org,884179-done@bugs.debian.org,885428-done@bugs.debian.org,887354-done@bugs.debian.org,889101-done@bugs.debian.org,889103-done@bugs.debian.org,889104-done@bugs.debian.org,892225-done@bugs.debian.org,897316-done@bugs.debian.org,900437-done@bugs.debian.org,908154-done@bugs.debian.org,916832-done@bugs.debian.org,916939-done@bugs.debian.org,
- Cc: gcc-6@packages.debian.org
- Subject: Bug#920171: Removed package(s) from unstable
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Thu, 07 Feb 2019 03:13:19 +0000
- Message-id: <E1gra7r-000G9u-7I@fasolo.debian.org>
Version: 6.5.0-2+rm Dear submitter, as the package gcc-6 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920171 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---