Greetings, and thanks so much for your report! It would be great if you
could configure with --enable-debug and provide the excellent gdb stack
trace you do now. But from what I can gather, the relevant cvs change
is:
--- gclttto/o/sgbc.c 2010-10-25 19:51:33.000000000 +0000
+++ gclttt/o/sgbc.c 2013-05-11 02:22:51.000000000 +0000
@@ -1068,7 +1068,7 @@
memprotect_bad_return,memprotect_no_signal,
memprotect_multiple_invocations,memprotect_no_restart,
memprotect_bad_fault_address,memprotect_success} memprotect_enum;
-static memprotect_enum memprotect_result;
+static volatile memprotect_enum memprotect_result;
static int memprotect_handler_invocations,memprotect_print_enable;
static void *memprotect_test_address;
Some recent change in gcc clobbered this silently, making all tests for
sgbc compatibility (a faster gbc relying on segfault address capture)
fail. Now the test succeeds, but the algorithm is failing for some
other reason down the line for you.
I'd like to find out why and fix that, as this is working on all current
Debian/Ubuntu machines. But in the meantime, if you want a workaround,
you can
./saved_ansi_gcl
> (fmakunbound 'si::sgc-on)
> (si::save-system "ff")
mv ff saved_ansi_gcl
and you should be good to go.
Take care,
--
Camm Maguire [email protected]
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
_______________________________________________
Gcl-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gcl-devel
