Hi, [email protected] skribis:
> I'm still seeing segfaults on rasbian on an rpi3. Have not tried > buildroot yet. > > That patch *did* fix a boatload of errors on arm, but this segfault is > an unrelated problem I think. Only happens on arm though. > > Here is a way to reproduce: > > In the test-suite/standalone dir: > while GUILE_JIT_THRESHOLD=0 make TESTS=test-language check-TESTS; do > :;done > > And then: > ../../meta/uninstalled-env ../../libtool --mode=execute gdb > ../../libguile/guile core > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x76f505cc in scm_is_string (x=0x0) at strings.h:293 > 293 return SCM_HAS_TYP7 (x, scm_tc7_string); > [Current thread is 1 (Thread 0x76fe6010 (LWP 21616))] > (gdb) bt > #0 0x76f505cc in scm_is_string (x=0x0) at strings.h:293 > #1 scm_string_to_symbol (string=0x0) at symbols.c:361 > #2 0x722df4cc in ?? () > Backtrace stopped: previous frame identical to this frame (corrupt > stack?) OK. On IRC you mentioned that this does not happen with GUILE_JIT_THRESHOLD=-1, right? Thanks, Ludo’.
