Re: XEmacs segfault

Ralf Angeli <[email protected]> writes:

> * David Kastrup (2005-02-01) writes:
>
>> Ralf Angeli <[email protected]> writes:
>>
>>> 21.4.16.  There was some discussion on the XEmacs lists about
>>> problems with shy groups in connection with Gnus.  In this case
>>> the result was a hang of XEmacs.  As far as I know this started
>>> with 21.4.16.  They recently found a fix for that but I don't know
>>> if this will fix as well the segfault I am seeing here.
>>>
>>> It wouldn't be a big deal to disable the regexps in concern for
>>> XEmacs in general, but if we get some feedback from the XEmacs
>>> people we could probably disable them for affected releases only.
>>
>> Maybe it is just a problem of initializing the data structures once.
>> Just do
>> (string-match "\\(\\(\\(\\(\\(\\(\\(\\(\\(\\(\\(\\(\\(\\(\\(\\(.\
>>                \\)\\)\\)\\)\\)\\)\\)\\)\\)\\)\\)\\)\\)\\)\\)\\)" "x")
>> once, and everything will turn out fine.
>>
>> Or something.  I hate life.
>
> Am I supposed to laugh or cry now?  After doing this, the segfault
> doesn't happen anymore.

Wait for feedback from the XEmacs folks.  The above is just blindly
poking around in the dark.  It may well be that it does not help
across a (save-match-data ...) or across the equivalent implemented
for process sentinels.

And honestly, it can hardly be called a solution.  It is not even a
workaround.  It is poking a hornets' nest right in the middle, in the
hope that the furious hornets will be exhausted by the time the guests
arrive.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum