Re: Core dumps in redisplay.

[David Kastrup <dak@gnu.org>]

"Jan D." <jan.h.d@swipnet.se> writes:

>> You wish.
>
> No. I know.  The only way the other threads can call xmalloc is if a
> signal handler is called in a non-main thread and then calls xmalloc.
> This should not happen, but if it does there is a bug somewhere.
>>
>
>> I am putting appropriate assertions in right now and expect to
>> report otherwise soon (the trace output is rather clear-spoken
>> about this).  I want to have this out of the way before I make an
>> Emacs/AUCTeX/preview-latex representation at a major GNU/Linux
>> conference Saturday and a workshop at a major TeX conference next
>> week without having the demos crash.  That's simply uncool.
>
>
> Please insert the thread id in the trace output, otherwise you can't
> know if it is another thread or a signal handler that calls xmalloc.

Apparently a signal handler.  I'd have an assertion get thrown if it
were another thread.  But I get my aborts not on the comparisons of
the thread id.

Ok, what is the beef with signal handlers?  Are they supposed to ever
throw a longjmp, whether in the course of Lisp exceptions or not?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum