This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/84439] call to backtrace fails after about 6000 iterations (32-bit executable)
- From: "ian at airs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 27 Feb 2018 13:25:14 +0000
- Subject: [Bug libfortran/84439] call to backtrace fails after about 6000 iterations (32-bit executable)
- Auto-submitted: auto-generated
- References: <bug-84439-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84439
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> ---
Yes, the intended use is certainly to create the state once per program. Each
time you create a new state and use it for a backtrace the code does a bunch of
initialization work reading the debug info. Much better to do that only once.
Plus there is the memory leak problem.
That said, yes, there should be a function to free a state. But this code
should really change to create the state once anyhow, if at all possible.