Re: crash

Thursday, 2 March 2000

        Michael Harnois <mdharnois(a)home.com&gt; writes:

You did say you could reproduce this?

...
     > If it is a crash, then it is xemacs and you need to give
more
     > info. C backtrace and version to be precise ('latest cvs' is
     > very ambiguous)
 #2  0x805608b in xrealloc (block=0x87148b8, size=9600)
     at /usr/src/xemacs-21.2/src/alloc.c:296 
This seems ok.. 

...
 #3  0x808cd18 in record_unwind_protect (
     function=0x81145fc <change_function_restore>, arg={gu = {
         type = Lisp_Type_Record, val = 36618428}, s = {bits = 0, 
         val = 73236856}, u = {bits = 0, val = 73236856}, ui = 146473712, 
       i = 146473712, v = 0x8bb02f0, cv = 0x8bb02f0})
     at /usr/src/xemacs-21.2/src/eval.c:4455
 #4  0x8111039 in signal_before_change (buf=0x8bb02f0, start=1, end=1)
     at /usr/src/xemacs-21.2/src/insdel.c:2174 
Maybe Hrvoje has an idea. Although this is before the extent
modification stuff.

The only thing is that your bracktrace looks very deep. Maybe we are
running out of stackspace somewhere?

Jan

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998