Stephen,
On Feb 7, 2012, at 8:50 AM, Stephen J. Turnbull wrote:
William Deegan writes:
> Greetings,
>
> I grabbed a stack trace by attaching to the process with gdb -p PID
> I've also included the log of the to the point it hangs (99% cpu forever.. left
it running overnight one time).
> Looks like it's hanging polling for some X event..
X.org was broken, and stayed that way for a long time.
https://trac.macports.org/ticket/18491
http://bugs.freedesktop.org/show_bug.cgi?id=20048
I suspect this is more of the same, as on several occasions they
claimed to have fixed this, but AFAIK they never fixed the real
problem (which is that _XtWaitForSomething() is documented not to
block, but it can block). MacPorts worked around it by configuring
libXt to use select() instead of poll() in this function.
If you can figure out where the POLLNVAL fd is coming from, or even
just which one it is, I'd like to fix that part of XEmacs.
I see from the bugs you have a long term exposure to this issue.
Should I reopen bug 18491? Because clearly its not fixed for Lion.
Also looks like from the opendesktop bugzilla that a patch was applied 1/10/2012 to fix
it.
Does this also fall into the never really fixed the real bug?
I saw in the bugs that there's an apple bug on poll. and now the man page has the
following:
BUGS
The poll() system call currently does not support devices.
So from all that is it reasonable that _XtWaitForSomething() shouldn't be calling
poll() on mac osx?
Barring that should stepping through the hung process yield the fd?
From the bug info where you posted stepping info it looks like you
might benefit from having some debug symbols, are those not available?
-Bill
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta