Your message dated Sun, 03 Sep 2017 13:54:52 +0200
with message-id <[email protected]>
and subject line Re: Bug#796562: lintian: Please identify lack of sanitation
compiler/linker flags
has caused the Debian Bug report #796562,
regarding Please identify lack of UBSAN compiler/linker flags
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 [email protected]
immediately.)
--
796562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796562
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lintian
Version: 2.5.36.1
Severity: wishlist
X-Debbugs-Cc: [email protected]
Hi,
we now have dpkg-buildflags(1) to turn on various sanitation
compiler/linker flags, such as -fsanitize=address.
Usage of such flags is not widespread yet in the Debian archive, but
my first attempts at using them on a few packages revealed bugs (some
of which, with potential security implications). It would be good to
have Lintian point maintainers at these flags, so that they learn
about them, try them out, and possibly discover security issues.
Cheers,
--
intrigeri
--- End Message ---
--- Begin Message ---
Bastien Roucaries:
> Le 20 juillet 2017 08:02:41 GMT+02:00, intrigeri <[email protected]> a
> écrit :
>>So I'm retitling this bug report to make it about UBSAN only,
>>i.e. compiling and linking programs with -fsanitize=undefined.
>>Note that by default, UBSAN only displays an error message at runtime
>>when a problem is detected, and then resumes execution.
> So not safe .... Display an error will change behaviour...
Fair enough :)
I'm thus closing this bug report. Let's come back to it once these
sanitizers are ready for production use.
--- End Message ---
