From: "H.J. Lu" <hjl.tools@gmail.com>
To: binutils@sourceware.org
Cc: amodra@gmail.com, gcc-patches@gcc.gnu.org
Subject: [PATCH 0/2] mmap: Avoid the sanitizer configure check failure
Date: Tue, 9 Apr 2024 07:24:33 -0700 [thread overview]
Message-ID: <20240409142435.1708867-1-hjl.tools@gmail.com> (raw)
When -fsanitize=address,undefined is used to build, the mmap configure
check failed with
=================================================================
==231796==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4096 byte(s) in 1 object(s) allocated from:
#0 0x7cdd3d0defdf in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69
#1 0x5750c7f6d72b in main /home/alan/build/gas-san/all/bfd/conftest.c:239
Direct leak of 4096 byte(s) in 1 object(s) allocated from:
#0 0x7cdd3d0defdf in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69
#1 0x5750c7f6d2e1 in main /home/alan/build/gas-san/all/bfd/conftest.c:190
SUMMARY: AddressSanitizer: 8192 byte(s) leaked in 2 allocation(s).
Define GCC_AC_FUNC_MMAP with export ASAN_OPTIONS=detect_leaks=0 to avoid
the sanitizer configure check failure.
H.J. Lu (2):
mmap: Avoid the sanitizer configure check failure
mmap: Avoid the sanitizer configure check failure
bfd/Makefile.in | 2 +-
bfd/aclocal.m4 | 1 +
bfd/configure | 5 +++++
bfd/configure.ac | 2 +-
binutils/Makefile.in | 2 +-
binutils/aclocal.m4 | 1 +
binutils/configure | 5 +++++
binutils/configure.ac | 2 +-
config/mmap.m4 | 12 ++++++++++++
config/no-executables.m4 | 4 ++--
ld/Makefile.in | 2 +-
ld/aclocal.m4 | 1 +
ld/configure | 5 +++++
ld/configure.ac | 2 +-
libctf/Makefile.in | 2 +-
libctf/aclocal.m4 | 1 +
libctf/configure | 5 +++++
libctf/configure.ac | 2 +-
libiberty/Makefile.in | 1 +
libiberty/acinclude.m4 | 2 +-
libiberty/aclocal.m4 | 1 +
libiberty/configure | 5 +++++
libsframe/Makefile.in | 1 +
libsframe/aclocal.m4 | 1 +
libsframe/configure | 5 +++++
libsframe/configure.ac | 2 +-
zlib/Makefile.in | 2 +-
zlib/acinclude.m4 | 1 +
zlib/configure | 7 -------
29 files changed, 64 insertions(+), 20 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-09 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 14:24 H.J. Lu [this message]
2024-04-09 14:24 ` [PATCH 1/2] " H.J. Lu
2024-04-09 14:24 ` [PATCH 2/2] " H.J. Lu
2024-04-09 23:08 ` [PATCH 0/2] " Sam James
2024-04-09 23:23 ` H.J. Lu
2024-04-10 5:39 ` Alan Modra
2024-04-10 10:56 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240409142435.1708867-1-hjl.tools@gmail.com \
--to=hjl.tools@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).