[Bug libbacktrace/105240] backtrace_pcinfo leaks memory

2022-04-12 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105240 --- Comment #5 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:3c742621ed28540cf42d4cfbc2bf03433cd26738 commit r12-8125-g3c742621ed28540cf42d4cfbc2bf03433cd26738 Author: Jonathan Wakely

[Bug libbacktrace/105240] backtrace_pcinfo leaks memory

2022-04-12 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105240 --- Comment #4 from Jonathan Wakely --- The report in comment 0 is from libstdc++ which uses a local static variable to hold the state. Modifying the comment 1 example to use a global: #include int cb_pcinfo(void*, uintptr_t, const char*,

[Bug libbacktrace/105240] backtrace_pcinfo leaks memory

2022-04-12 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105240 Ian Lance Taylor changed: What|Removed |Added CC||ian at airs dot com --- Comment #3

[Bug libbacktrace/105240] backtrace_pcinfo leaks memory

2022-04-12 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105240 --- Comment #2 from Jonathan Wakely --- I thought it would be OK to just use the malloc configuration unconditionally within libstdc++, but it looks like I need to include the configure checks for mman.h and use mmap whenever possible. It might

[Bug libbacktrace/105240] backtrace_pcinfo leaks memory

2022-04-12 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105240 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2022-04-12