Re: macOS status
"Kirill A. Korinsky" <[email protected]>
| Newsgroups | gmane.lisp.gcl.devel |
|---|---|
| Message-ID | <[email protected]> |
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 <[email protected]> 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
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE3/KLNtcfWfLw7JxqmNjZhndZIm4FAmWImU8ACgkQmNjZhndZ Im6ELQ//QtGlfyAeKZusY2FZtJO2VAEF2ZO9iscug5uvRec2t1kN+azl/TmLAQ9d Gg7Clzbr3emF1QQCt20tqy5kQj/TZ+e25mLuJUEVzViIAbsJKZJLQ03OSMcGoAKa TC36Aijjt/c3gjEimBrpuZXEShfdPr1rI+I5vPhp2840PLdJHS7oNxIk3LhImB2B H8SnAzo0E55cRIt8m9znrmOgvcv57Yq1bvb/wg2PZXyf54mFz22FvM/vJgHi3fRq 6Kpj81Qia23zgcoGx8VRzbHPZHjOUMQyX6vMWh9QipL69mO+UAJDSq4xlPHbwHax GnK9+BIYoOcox7c/YFKn0I83RPjPf1bqRNi/3csawW/Pkq+xGQn9os1pGSVtlgNZ vjh32dUNdPXGpXkIbZc4FZcGFvU/Yk1NJRGQJjx+8gdFM1/QwobFTvRSd9LM9B/p vLSxtKN1ohO7zt46D0EYPfP/J+ABVSXybxR1ftB7TPr3IZiVLM08X97+Go1K8ptn fegZ9w1gIe21XPaKtF/8nFuMm2m/ww/qxXfgXAvgjPOznaRo6BRzmy90AtIHH/hk Exklz4wGfHYuns+W8tUTAx7xELo0BmsTcLdH1okHGsnKIqRvbw+yacGaySd5YzUu l6dLYkACGfJt1HnAZK3Kqa5cShry0VD5rrvBmOZG/tBTU4znIBk= =vII1 -----END PGP SIGNATURE-----