[Bug: 21.5-b28] Crash after server password prompt(ERC)

[Stephen J. Turnbull]

It's me FKtPp ;) writes:

 > #8  0x00000000004b5d16 in Ffuncall (nargs=3, args=0x7ffffe0ddba8)
 >     at eval.c:3928
 > #9  0x0000000000470d81 in execute_optimized_program (
 >     program=0x15dacf0 "~\033~\032\r~\034~\021~\211\020\026\035~\026\036\016\037~\004~ \210~ \210\r\026 ~~!\210~~\f~a~\037~\rA@!~\025~\rA at GU~\r~\rA@~H!~\004~\035~\032\f~a~\004~\022\f~s~\004~\n\f~a~\004\002~\"\210~\r~\"\210~ ~\v~~\016!\"\210~~!\210+~\207~\a", stack_depth=6, constants_data=0xb107e0)
 >     at bytecode.c:862

Your backtrace seems to be corrupt (the '~' characters).  If you
happen to have a clear copy that would be nice (but don't kill
yourself to get it, it looks like the funcall in frame #8 is more
directly related).

If you have the core file, start gdb /path/to/xemacs, then source
.gdbinit, and do "up 9" then "pobj constants_data".  (I think that's
the right place to do it, you may need to be at frame #8.)  Also in
frame #8 I'd love to have a look at args[0], args[1], and args[2]
under pobj.

It might also be useful to use ldp on those, but that needs to be done
on a running xemacs, the core file isn't good enough.

Since you seem to be eliciting a lot of crashes, may I recommend that
you run xemacs under gdb all the time?  This doesn't cost much except
a few dozen KB of RAM, and some weirdness with C-z (which tends to
throw you into the debugger rather than whatever you had bound to that
key).

Also, your crashes seem to be kinda intermittent (eg, this one looks
like a garbage collection crash) which means that we've probably got a
bug pretty far away from where the crash actually happened.  If you
could hang on to your crashed process until we've had a chance to ask
it a few questions, that can often be of enormous help in tracking
these down.  Don't forget to mention it, keeping crashed processes
does use up system resources, including your freedom to restart the
system.  We wouldn't want to keep you waiting!