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 libbacktrace/105240] backtrace_pcinfo leaks memory
Date: Tue, 12 Apr 2022 21:39:44 +0000	[thread overview]
Message-ID: <bug-105240-4-pI5ov9Hs5c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105240-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:3c742621ed28540cf42d4cfbc2bf03433cd26738

commit r12-8125-g3c742621ed28540cf42d4cfbc2bf03433cd26738
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Apr 12 17:56:45 2022 +0100

    libstdc++: Prefer to use mmap instead of malloc in libbacktrace

    As reported in PR libbacktrace/105240, libbacktrace leaks memory when
    using malloc for allocations. I originally thought it would be simpler
    to just use malloc unconditionally (because it's supported on all
    targets) but the leaks make that problematic.

    This adds libbacktrace's detection for mmap to the libstdc++
    configury, so that we use mmap.c and mmapio.c when possible. This avoids
    the leaks seen previously, at least on linux.

    libstdc++-v3/ChangeLog:

            * acinclude.m4 (GLIBCXX_ENABLE_BACKTRACE): Check for mmap.
            * config.h.in: Regenerate.
            * configure: Regenerate.

      parent reply	other threads:[~2022-04-12 21:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 14:49 [Bug libbacktrace/105240] New: " redi at gcc dot gnu.org
2022-04-12 14:50 ` [Bug libbacktrace/105240] " redi at gcc dot gnu.org
2022-04-12 14:52 ` redi at gcc dot gnu.org
2022-04-12 16:31 ` ian at airs dot com
2022-04-12 17:39 ` redi at gcc dot gnu.org
2022-04-12 21:39 ` cvs-commit at gcc dot gnu.org [this message]

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-105240-4-pI5ov9Hs5c@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).