[Bug libbacktrace/87529] libbacktrace API forces users to have memory leaks

[ian at airs dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87529

Ian Lance Taylor  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Ian Lance Taylor  ---
Thanks, closing this PR.

[Bug libbacktrace/87529] libbacktrace API forces users to have memory leaks

[antoshkka at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87529

--- Comment #3 from Antony Polukhin  ---
Comment is enough to make me happy. Thanks!

[Bug libbacktrace/87529] libbacktrace API forces users to have memory leaks

[ian at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87529

--- Comment #2 from ian at gcc dot gnu.org  ---
Author: ian
Date: Fri Oct  5 14:09:07 2018
New Revision: 264871

URL: https://gcc.gnu.org/viewcvs?rev=264871=gcc=rev
Log:
PR libbacktrace/87529
* backtrace.h: Document that backtrace_create_state should be
called only once.

Modified:
trunk/libbacktrace/ChangeLog
trunk/libbacktrace/backtrace.h

[Bug libbacktrace/87529] libbacktrace API forces users to have memory leaks

[ian at airs dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87529

Ian Lance Taylor  changed:

   What|Removed |Added

 CC||ian at airs dot com

--- Comment #1 from Ian Lance Taylor  ---
Programs are expected to call backtrace_create_state once.  There's no reason
to call it more than once.

Yes, I agree that it would be nice to have backtrace_free_state, but it's hard
to write correctly.  And it's hard to see why any program would want to call
it, as it would be less efficient.