emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs, Mac OS X Yosemite and restarts after sleep


From: Harald Hanche-Olsen
Subject: Re: Emacs, Mac OS X Yosemite and restarts after sleep
Date: Mon, 24 Nov 2014 09:42:20 +0100
User-agent: Postbox 3.0.11 (Macintosh/20140602)

Paul Michael Reilly wrote:
The final test was to use Emacs 25 built around the time Eric announced
the git conversion ready for testing. This test also failed. Conclusion:
Emacs and Yosemite do not play nice together.

That conclusion seems a bit strong: I am running emacs compiled straight from the git repo on Yosemity with no problem. But perhaps I just don't run into your particular circumstances.

So I have two questions: 1) would someone with a recent model MacBook
Pro, running Yosemite and either Emacs 24.4 or 25.0.90 (fullscreen mode)
please run the experiment and report back your results;

Just to see if I have this straight, the proposed experiment is

1. Start emacs (with or without -Q)
2. Put it in “native” fullscreen mode (using the green button without the Alt key)
3. Let the machine sleep for some hours
4. Wake the machine, watch emacs die and take the machine with it

I have two questions.

Is #2 essential? It does not crash if emacs is not in fullscreen mode when you put the machine to sleep?

Is #3 essential? A sleep measured in minutes will not trigger the problem? If so, debugging will be a drawn-out affair.

I have a macbook air (not pro), and it is not very recent, but I can run this experiment anyhow, to see if I can get a crash.

2) can someone
suggest methods I can use to log relevant information on Emacs'
termination

Have you looked for a crashlog in ~/Library/Logs/DiagnosticReports/?
Other than that, I have no suggestions. You might try running it under gdb, in a screen or tmux session with logging turned on. But since the machine also crashes, there is a good chance that this happens before any writing of log data can happen. But still, you should look in /var/log/system.log and see if there is any hint to be had there.

– Harald



reply via email to

[Prev in Thread] Current Thread [Next in Thread]