public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/102911] AddressSanitizer: CHECK failed: asan_malloc_linux.cpp:46
Date: Wed, 19 Jan 2022 19:49:52 +0000	[thread overview]
Message-ID: <bug-102911-4-IRSYFqONOv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102911-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102911

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:666eb85627e961db200dd5db639a1831d81188e1

commit r10-10408-g666eb85627e961db200dd5db639a1831d81188e1
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Fri Dec 17 11:08:32 2021 -0800

    libsanitizer: Cherry-pick LLVM release/13.x commit d96358a28193

    Cherry-pick from LLVM release/13.x branch:

    commit d96358a2819399a2abb60ad3b26444ab7b4409cf
    Author: MichaŠGórny <mgorny@moritz.systems>
    Date:   Mon Dec 13 22:28:26 2021 +0100

        [compiler-rt] Increase kDlsymAllocPoolSize to fix test failures

        Increase kDlsymAllocPoolSize on the release branch as discussed on bug
        51620, as an alternative to backporting
        cb0e14ce6dcdd614a7207f4ce6fcf81a164471ab and its dependencies.
        The minimum size is 8192, as needed for the following test to pass:

          AddressSanitizer-i386-linux :: TestCases/Linux/long-object-path.cpp

        Fixes #51620

            PR sanitizer/102911
            * asan/asan_malloc_linux.cpp (kDlsymAllocPoolSize): Set it to
            8192 on Linux.

    (cherry picked from commit 8c0f58cd71ec3afcce5abf10c750ec494e88232b)

  parent reply	other threads:[~2022-01-19 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23 23:37 [Bug sanitizer/102911] New: " hjl.tools at gmail dot com
2021-10-24  0:35 ` [Bug sanitizer/102911] " hjl.tools at gmail dot com
2021-10-24 11:52 ` hjl.tools at gmail dot com
2021-11-13 13:18 ` cvs-commit at gcc dot gnu.org
2021-11-13 13:23 ` hjl.tools at gmail dot com
2021-11-14 22:36 ` pinskia at gcc dot gnu.org
2022-01-12  2:34 ` cvs-commit at gcc dot gnu.org
2022-01-19 19:49 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-19 21:21 ` cvs-commit at gcc dot gnu.org
2022-01-19 21:23 ` hjl.tools at gmail dot com

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=bug-102911-4-IRSYFqONOv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).