Re: crypt (or tar) breakage?
>>>> "SL" == SL Baur <steve(a)xemacs.org>
writes:
SL> 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...
SL> O.K. I've just noticed a worse problem.
SL> With current CVS sources (almost b63) if I do:
SL> xemacs -vanilla
SL> M-: (require 'crypt)
SL> C-x C-f cvs-1.10.5.tar.gz
SL> When I hit enter at the prompt I get a core dump:
SL> Fatal error (11).
SL> ...
SL> Lisp backtrace follows:
SL> # bind (inhibit-quit)
SL> passwd-read-key-sequence("Encryption key for cvs-1.10.5.tar? [RET to
SL> ignore]:
SL> ")
SL> ...
SL> (gdb) where
SL> #0 0x3ff800ec508 in kill () from /usr/shlib/libc.so
SL> #1 0x1200c3980 in fatal_error_signal (sig=1076522752) at emacs.c:262
SL> #2 0x120119810 in mule_encode (encoding=0x1, src=0x11fff6a30
SL> "＠A\r\200\003",
SL> dst=0x1200675f8, n=536832832) at file-coding.c:2439
SL> warning: Hit beginning of text section without finding
SL> warning: enclosing function for address 0x11fff7058
SL> Sigh. I'm going to have to track this down before making
SL> 21.0.63 and 21.2.11.
Huh? I am running (emacs-version) "XEmacs 21.0 \"Pyrenean63\" [Lucid]
(i386-pc-win32) of Sat Feb 06 1999 on ZJ75T" already. Did you mean to
say 21.0.64?
Adrian
--
Adrian Aichner Teradyne GmbH, European Design Center
Integra Test Division Telephone +49/89/41861(0)-208
Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?)
D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com