nbecker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org:
No, but if I do xemacs -q, load-lib crypt, then visit the file it
works. So you're correct that it is some interaction with some other
package. I'll try to isolate it, but my .emacs is getting pretty
large, so this may take some time...
O.K. I've just noticed a worse problem.
With current CVS sources (almost b63) if I do:
xemacs -vanilla
M-: (require 'crypt)
C-x C-f cvs-1.10.5.tar.gz
When I hit enter at the prompt I get a core dump:
Fatal error (11).
...
Lisp backtrace follows:
# bind (inhibit-quit)
passwd-read-key-sequence("Encryption key for cvs-1.10.5.tar? [RET to ignore]:
")
...
(gdb) where
#0 0x3ff800ec508 in kill () from /usr/shlib/libc.so
#1 0x1200c3980 in fatal_error_signal (sig=1076522752) at emacs.c:262
#2 0x120119810 in mule_encode (encoding=0x1, src=0x11fff6a30 "@A\r\200\003",
dst=0x1200675f8, n=536832832) at file-coding.c:2439
warning: Hit beginning of text section without finding
warning: enclosing function for address 0x11fff7058
Sigh. I'm going to have to track this down before making 21.0.63 and
21.2.11.