Sat, 8 Oct 2011 (10:01 +0900 UTC) Stephen J. Turnbull wrote:
Aidan Kehoe writes:
> I suspended my Mac to disk overnight, and got back from college an hour or
> so ago. I woke it up, and thirty seconds or so later XEmacs disappeared. The
> backtrace from the core file is below; it seems there is some context where
> async_timeout_happened can become non-zero when async_timer_queue is empty.
With a quick look at the XEmacs code, I can see only two possibilities:
(1) a wild pointer;
(2) Mac OS X is delivering an unexpected SIGALRM or similar.
I wonder if that correlates with suspending.
There used to be a problem in X11 (OS X) when a network transition
occurred during sleep (i.e. the Mac goes to sleep with one IP and wakes
to find it has another IP). Individual programs or the entire xserver
You're probably wondering why I'm here. So am I--so am I.
8:52 up 17 days, 21:37, 1 user, load averages: 0.07 0.10 0.08
XEmacs-Beta mailing list