Re: Crash in XEmacs 21.0 "20 minutes to Nikko" with gnuserv/gnuclient
Jan Vroonhof sneezed over the keyboard.
The gobbets of snot hit the keys and miraculously produced :
(Sorry for the delay in getting back to you...been a bit busy...)
[snip]
obscurity <obscurity(a)obscure.org> writes:
> Your wish is my command. Just killed gpm and gave it another go,
I meant compiling without GPM support. However I think this already
confirms my hunch it is related to GPM. I think I know how to fix the
crash (could you try to use the (untested) patch at the end?).
Done, and yes, it now works fine :)
But
to fix the real problem is harder. We simply should not close the GPM
connection when there are still linux consoles open. This would
require some kind of reference counting or scanning all the consoles
for open connection
> time when I exited from gnuclient on the second virtual console, xemacs
> exited (without crashing) on the original virtual console. Not having used
> gnuserv/gnuclient before, I'm not sure if it's supposed to do this (it
would
> make more sense to me to just exit the gnuclient and leave the host xemacs
> running), but at least it doesn't dump core.
No it is not supposed to do that. I think it is another bug, unrelated
to this. I cannot reproduce that however. Can you with "xemacs -vanilla"?
Uh...this turned out to be a problem with the interface between keyboard and
chair. I was exiting the gnuclient with 'save-buffers-kill-emacs' rather
than 'delete-frame'. I need to find a way of getting my .emacs to set my
keys differently if I'm running gnuclient rather than xemacs :)
--
obscurity.
"Only the great masters of style ever succeed in being obscure." - Oscar Wilde