Jan Vroonhof sneezed over the keyboard.
The gobbets of snot hit the keys and miraculously produced :
obscurity <obscurity(a)obscure.org> writes:
Do you have a real name by chance?
I do (of course), but I do not use it online. For long, complicated, and
completely off-topic reasons :)
I tend to interact better with real
people.
Well, please let me reassure you that I *am* a real person. Even my doctor
says so :)
> I've got an easily-reproduceable crash in XEmacs 21.0
"20 minutes to Nikko",
> when using gnuserv/gnuclient. If I start xemacs, run gnuserv-start, flip to
> another virtual console (this is on linux) run gnuclient, and then exit
> gnuclient (with or without doing any actual editing), then xemacs on the
> original virtual console barfs, with the following :
For me I get a crash on exit when on 21.2.
> |#5 0x80ac5a7 in assert_failed (file=0x8204e49 "event-Xt.c", line=1863,
> | expr=0x8204fd8 "closure") at emacs.c:2608
> |#6 0x818c960 in emacs_Xt_unselect_console (con=0x841df10) at event-Xt.c:1863
> |#7 0x80dd0ec in event_stream_unselect_console (con=0x841df10)
Are you using GPM?
Yup.
Could you try without it.
Your wish is my command. Just killed gpm and gave it another go, and this
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.
P.S. Aren't all the linux consoles really one console in the
XEmacs
sense anyway?
I'm not sure what you mean by 'one console in the XEmacs sense', so I
can't
answer I'm afraid.
--
obscurity.
"Only the great masters of style ever succeed in being obscure." - Oscar Wilde