Re: GC crashes

[David Kastrup]

Chong Yidong <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>
>>>   #0  initialize_cut_buffers (display=0x8, window=16843009) at 
>>> xselect.c:2316
>>>     data = (unsigned char *) 0x820c124 "\213\367\017\b\001"
>>>
>>>   #1  0x080ff866 in Fx_rotate_cut_buffers_internal (n=8) at xselect.c:2470
>>>     window = 73
>>>     props = {0, 0, 0, 0, 136364324, 138120105, 3220375768, 135779857}
>>>     display = (Display *) 0x8748060
>>>     sf = (struct frame *) 0x856d418
>>
>> from etc/DEBUG:
>>
>>     ** When you are trying to analyze failed assertions, it will be
>>     essential to compile Emacs either completely without optimizations or
>>     at least (when using GCC) with the -fno-crossjumping option.  Failure
>>     to do so may make the compiler recycle the same abort call for all
>>     assertions in a given function, rendering the stack backtrace useless
>>     for identifying the specific failed assertion.
>
> This was a bus error, not a failed assertion.  Also, I believe he
> compiled Emacs with `-O0'.

Ah, ok.  However, I found that backtraces are less than reliable in
such situations.  If he has the ability to set breakpoints or
watchpoints that trigger before the actual bus error occurs, the
probability of a useful backtrace will be quite larger.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum