diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2022-04-12 17:56:45 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2022-04-12 22:38:31 +0100 |
| commit | 3c742621ed28540cf42d4cfbc2bf03433cd26738 (patch) | |
| tree | fb0b6e89fda4b8eeffd65d81304b4e118691e188 /gcc | |
| parent | b2c007b87dcd5db5d59447de2081777aea66f35f (diff) | |
| download | gcc-3c742621ed28540cf42d4cfbc2bf03433cd26738.zip gcc-3c742621ed28540cf42d4cfbc2bf03433cd26738.tar.gz gcc-3c742621ed28540cf42d4cfbc2bf03433cd26738.tar.bz2 | |
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.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions