JVDptt

Many thanks, Phoebe - yes, that clarifies many things. All the best, Jason On Fri, 17 Jun 2022 at 16:08, Phoebe Goldman ***@***.***> wrote: > *code-points-to-unicode1-names*` is an internal variable,...

Coredump details : ``` $ gdb boehmprecise/clasp /tmp/iclasp.coredump GNU gdb (GDB) 15.0.50.20240129-git Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free...

I'd suggest some sort of re-entry detector in core::lisp_error() ? ie. core::lisp_error() calls fboundp() which calls core::lisp_error() - this recursion needs to be detected and limited.

Actually, I am building with latest binutils-2.42 in /usr/local/bin /usr/local/lib64, I will try re-building with standard system binutils-2.39-16 .

Yes, exactly the same error and coredump occur using either binutils v2.39-16 or binutils v2.42 . What Clang / LLVM + binutils version do you use for compiling ? Evidentally...

With this patch, infinite recursion and coredump is avoided, but unfortunately the build still fails , printing the message: ``` lisp_error -> Error # initializers: (NIL NIL) ``` , unfortunately...

Thanks for taking a look, Alex . The recursion path is documented in the "Coredump Details" comment above : ``` (gdb) where #0 core::lisp_error (datum=datum@entry=..., arguments=...) at ../src/core/foundation.cc:1360 #1 0x0000000000f4dc36...

Thanks all for taking a look at this . It is still happening 100% for me, either checking out main clasp repo, https://github.com/clasp-developers/clasp , or the sub-module https://github.com/clasp-developers/ansi-test.git under dependencies/ansi-test....

Traceroute to github.com : ` 1 router (192.168.37.126) 9.779 ms 9.691 ms 9.829 ms 2 100.112.0.5 (100.112.0.5) 152.032 ms 151.995 ms 152.526 ms 3 172.24.114.113 (172.24.114.113) 69.827 ms 69.997 ms...

I guess the "fix" is to run tcpdump in background :-) ... weird!