Re: [Bug: 21.5-b31] Crash in timeout handling code.
- First Post
- Replies
- Stats
-
Go to
- ----- 2024 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2005 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2004 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2003 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2002 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2001 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2000 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1999 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1998 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
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
would crash.
--
You're probably wondering why I'm here. So am I--so am I.
-Frank Zappa
8:52 up 17 days, 21:37, 1 user, load averages: 0.07 0.10 0.08
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Wednesday, 12 October
Wed, 12 Oct
6:56 a.m.
New subject: [Bug: 21.5-b31] Crash in timeout handling code.
robert delius royar writes:
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
would crash.
Thanks for the info!
I don't see how remote clients could avoid crashing -- the X server
goes away, but the X server needs to be robust to that.
I-guess-I-haven't-seen-it-because-Rust-Never-Sleeps-ly y'rs,
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
robert delius royar
Wednesday, 12 October
Wed, 12 Oct
1:13 p.m.
New subject: [Bug: 21.5-b31] Crash in timeout handling code.
Wed, 12 Oct 2011 (14:56 +0900 UTC) Stephen J. Turnbull wrote:
robert delius royar writes:
> 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
> would crash.
Thanks for the info!
I don't see how remote clients could avoid crashing -- the X server
goes away, but the X server needs to be robust to that.
I-guess-I-haven't-seen-it-because-Rust-Never-Sleeps-ly y'rs,
To be more specific, the crashes would occur on a machine where the
server was on the machine where the transition occurred and the clients
were also.
I never see this with my MBP (just in the past with my old PowerBook).
So the problem seems to have been fixed soon after Jeremy took over
maintaining X11.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4790
days inactive
4794
days old
2 comments
2 participants
tags (0)
participants (2)
-
robert delius royar -
Stephen J. Turnbull