This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libfortran/84439] call to backtrace fails after about 6000 iterations (32-bit executable)


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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]