On Tue, Apr 4, 2017 at 5:05 AM, <bas...@starynkevitch.net> wrote: > > I just discovered that backtrace_create_state should be called once, that it > is returning some heap-allocated data (which cannot be free-d, because there > is no > backtrace_destroy_state routine). > > I suggest the attached patch (against GCC trunk r246678) which just improves > the comment describing that function.
You are adding that backtrace_create_state should be called "(probably at startup, e.g. early in main)"? But that is not accurate. It's perfectly reasonable to do what GCC itself does, which is call backtrace_create_state only when it encounters an internal compiler error (in diagnostic_action_after_output in gcc/diagnostic.c). How about we just add backtrace_destroy_state? Ian
