On Fri, Nov 30, 2018 at 9:29 PM Janne Blomqvist
wrote:
> On Fri, Nov 30, 2018 at 9:07 PM Thomas Schwinge
> wrote:
>
>> Hi!
>>
>> On Thu, 22 Nov 2018 11:17:24 +0200, Janne Blomqvist <
>> blomqvist.ja...@gmail.com> wrote:
>> > From backtrace.h for backtrace_create_state:
>> >
>> >Calling this
On Fri, Nov 30, 2018 at 9:07 PM Thomas Schwinge
wrote:
> Hi!
>
> On Thu, 22 Nov 2018 11:17:24 +0200, Janne Blomqvist <
> blomqvist.ja...@gmail.com> wrote:
> > From backtrace.h for backtrace_create_state:
> >
> >Calling this function allocates resources that can not be freed.
> >There is n
Hi!
On Thu, 22 Nov 2018 11:17:24 +0200, Janne Blomqvist
wrote:
> From backtrace.h for backtrace_create_state:
>
>Calling this function allocates resources that can not be freed.
>There is no backtrace_free_state function. The state is used to
>cache information that is expensive to
On 11/29/18 11:37 PM, Janne Blomqvist wrote:
PING!
LGTM,
OK and thanks
Jerry
(for the GCC-7 branch, I'll commit it after the 7.4 release)
On Thu, Nov 22, 2018 at 11:17 AM Janne Blomqvist
wrote:
From backtrace.h for backtrace_create_state:
Calling this function allocates resources
PING!
(for the GCC-7 branch, I'll commit it after the 7.4 release)
On Thu, Nov 22, 2018 at 11:17 AM Janne Blomqvist
wrote:
> From backtrace.h for backtrace_create_state:
>
>Calling this function allocates resources that can not be freed.
>There is no backtrace_free_state function. The
>From backtrace.h for backtrace_create_state:
Calling this function allocates resources that can not be freed.
There is no backtrace_free_state function. The state is used to
cache information that is expensive to recompute. Programs are
expected to call this function at most once an
