* Andrew Pinski via Gcc:
> On Wed, Aug 28, 2024 at 2:37 PM David Malcolm via Gcc wrote:
>>
>> I've been debugging a use-immediately-after-free bug involving obstacks
>> (the bug isn't in trunk; I found it whilst testing one of my patches).
>>
>> It was only visible as a crash when it happened tha
Andrew Pinski via Gcc writes:
> On Wed, Aug 28, 2024 at 2:37 PM David Malcolm via Gcc wrote:
>>
>> I've been debugging a use-immediately-after-free bug involving obstacks
>> (the bug isn't in trunk; I found it whilst testing one of my patches).
>>
>> It was only visible as a crash when it happen
On Wed, Aug 28, 2024 at 2:37 PM David Malcolm via Gcc wrote:
>
> I've been debugging a use-immediately-after-free bug involving obstacks
> (the bug isn't in trunk; I found it whilst testing one of my patches).
>
> It was only visible as a crash when it happened that the call to
> obstack_free led
I've been debugging a use-immediately-after-free bug involving obstacks
(the bug isn't in trunk; I found it whilst testing one of my patches).
It was only visible as a crash when it happened that the call to
obstack_free led to the underlying buffer being freed. Most of the
time, the bug was dorm
