This is the mail archive of the
cygwin
mailing list for the Cygwin project.
stabilizing cygwin emacs, was: emacs Fatal error 11
- From: Thomas L Roche <tlroche at us dot ibm dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 18 Feb 2004 09:32:35 -0500
- Subject: stabilizing cygwin emacs, was: emacs Fatal error 11
"Etienne Huot" Wed, 18 Feb 2004 13:05:22 +0100
> I have tried the latest snapshot 20040217, it worked for several
> hours, but now it crashes almost every 2 minutes. I'm gonna switch
> to 20040216 to see what happens.
Well, so far I've had no crashes with 20040217, but obviously I
haven't been running it very long. Something you might want to
consider (I haven't done it, and YMMV) is rebasing:
Thomas L Roche Tue, 3 Feb 2004 16:09:47 -0500
>>>> ~29 Jan I upgraded to cygwin-1.5.6-1, emacs-21.2.1, and whatever
>>>> the latest XFree86 was then, along with the other goodness
>>>> cygwin's setup advised me to get. Since then emacs life has been
>>>> bad[:] emacs windows disappear, apparently randomly, although
>>>> lately I'm convinced that emacs crashes are more likely when I'm
>>>> either resizing or minimizing its windows.
Al Williams 13 Feb 2004 13:18:32 -0800
>>> I was having this problem. Rebasing the Cygwin DLLs seems to have
>>> cleared it up. Install rebase using setup and then exit all Cygwin
>>> stuff (including httpd, etc.). Then open a plain shell (not an
>>> xterm) and enter:
>>> rebaseall -v
Al Williams 16 Feb 2004 17:24:41 -0800
>> Each DLL has a preferred load address. If it can be loaded at that
>> address, fine. If not, Windows will put it at a different address.
>> Apparently (and I don't know this for sure) the Cygwin stuff
>> assumes all DLLs will be at the same address in each process space
>> (as would always be the case in Win98, for example). So if DLLs
>> conflict and are loaded in different order, it is possible for
>> process A to have DLLx at addresss Z and process B has DLLy at the
>> same address and Cygwin apparently detects this and stops.
>> Rebasing moves the DLL load addresses to make this less likely.
>> If you google on:
>> rebaseall cygwin
>> You'll see this is a common issue with certain packages. I don't
>> think it will really hurt anything. If you are really worried, copy
>> all the DLL files under c:\cygwin (or whatever your CYGROOT is)
>> before you start.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/