>>>> AA == Adrian Aichner writes:
AA> Failing to
build due to this:
AA>
AA> KKCC backtrace overflow, adjust KKCC_BT_STACK_SIZE.
AA> Maybe it is a loop?
AA>
AA> Fatal error: assertion failed, file
AA> c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src\alloc.c, line
AA> 3382,
AA> ABORT()
AA> Fatal error.
I was way too stingy with the backtrace stack size. This patch bumps it up
to 256k. Please test it and increase it if compilation still fails. I'll
test on cygwin later today myself.
Also the make check failures reported in your other mails are due to the
backtrace size limit, it just has to be increased (potentially for the mule
tests), so that it is not crashing anymore.
If more of this crash reports occur, I'll drop the idea of making the
backtrace stack a static data structure and switch to a dynamically
allocated one.
Index: alloc.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/alloc.c,v
retrieving revision 1.108
diff -u -r1.108 alloc.c
--- alloc.c 11 Mar 2005 08:42:36 -0000 1.108
+++ alloc.c 12 Mar 2005 14:57:42 -0000
@@ -3323,7 +3323,7 @@
static int kkcc_gc_stack_size;
#ifdef DEBUG_XEMACS
-#define KKCC_BT_STACK_SIZE 4096
+#define KKCC_BT_STACK_SIZE 262144
static struct
{
--
Marcus