[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Memory exhausted error
|
From: |
Eric Blake |
|
Subject: |
Re: Memory exhausted error |
|
Date: |
Thu, 17 Dec 2020 09:07:19 -0600 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 |
On 12/16/20 10:27 PM, lexxmark.dev@gmail.com wrote:
> I’m porting flex/bison on windows and build M4 code inside executable.
>
> After upgrading gnulibs I caught a runtime error “memory exhausted” in
> macro.c file.
What do you mean by updating gnulib, pointing the submodule to a newer
commit? Yes, there have been a number of changes in more recent gnulib
that may require some porting efforts in the matching m4 code to follow
new semantics from what gnulib offers, and it looks like you have found
one of them.
>
> obstack_blank (&argv_stack, -argc * sizeof (token_data *)); << crash
> here!!!
> Line 390
>
> }
>
> It seems now obstack_blank function doesn’t allow negative numbers (see
> /lib/obstack.h file)
That matches gnulib/NEWS for 2014-10-29; the fix is to use
obstack_blank_fast() instead, when using a gnulib newer than that date.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org