Well, Here a king of chicken and the egg problem: as side effect get_gc_environ setup mem_multiple to 1.0 and after that override it to value which is getting via scanf which trigger the loop.
macOS has quite paranoid memory allocation and reset everything to. This means that mem_multiple is 0 without call get_gc_environ and as soon as I add GCL_MEM_MULTIPLE env variable (or any other one), it triggers the loop. -- wbr, Kirill > On 24. Dec 2023, at 20:14, Camm Maguire <c...@maguirefamily.org> wrote: > > Greetings, and thanks so much! Extremely helpful. I'm amazed you ever > got past this. > > gcl_init_alloc has to finish without calling malloc. macosx sscanf > called via get_gc_environ does. Just comment out the call to > get_gc_environ in update_real_maxpage and please let me know if this > goes away. Ideally you could run under gdb, breaking at gcl_init_alloc > and alloc.c:malloc, (gdb) r ./ <foo, and (gdb) fin when the former is > reached. Make sure it finishes without calling malloc again. >
signature.asc
Description: Message signed with OpenPGP
