Re: toolchain/54090: gcc -fsanitize=address creates an unusable binary on amd64

[Alexander Nasonov <alnsn%yandex.ru@localhost>]

The following reply was made to PR toolchain/54090; it has been noted by GNATS.

From: Alexander Nasonov <alnsn%yandex.ru@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: toolchain-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
	netbsd-bugs%netbsd.org@localhost, alnsn%netbsd.org@localhost
Subject: Re: toolchain/54090: gcc -fsanitize=address creates an unusable
 binary on amd64
Date: Sun, 31 Mar 2019 12:43:56 +0100

 Kamil Rytarowski wrote:
 >  If this is enough, I propose to disable detect_leaks unconditionally and
 >  leave it for future.
 
 Disabling it silently isn't ideal because some people may falsely
 assume that their software is leak free.
 
 In a typical setup (when /proc is mounted with nolinux), it doesn't
 hang but prints some useful hints:
 
  $ ./a.out
  ==373==Can't open /proc/6440/task for reading.
  ==6440==LeakSanitizer has encountered a fatal error.
  ==6440==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1
  ==6440==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
 
 Can we add another hint here about detect_leaks?
 
 -- 
 Alex