public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libbacktrace/105240] backtrace_pcinfo leaks memory Date: Tue, 12 Apr 2022 16:31:45 +0000 [thread overview] Message-ID: <bug-105240-4-hjJS99h4bb@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 Ian Lance Taylor <ian at airs dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian at airs dot com --- Comment #3 from Ian Lance Taylor <ian at airs dot com> --- mmap is definitely preferred. The malloc implementation is only there to support systems without mmap. That said I'm not sure I understand the valgrind report. Some of that memory is not lost as long as the program has a pointer to the backtrace_state. It's true that there is no way to release all memory allocated by the state. That is not a goal, as I expect that programs will allocate a backtrace_state and use it until the program is complete. What kinds of reports do you see if you put the backtrace_state in a global variable?
next prev parent reply other threads:[~2022-04-12 16:31 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 [this message] 2022-04-12 17:39 ` redi at gcc dot gnu.org 2022-04-12 21:39 ` cvs-commit at gcc dot gnu.org
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-hjJS99h4bb@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: linkBe 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).