xemacs crash in package update

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.0 "20 minutes to Nikko" [Lucid] (i686-redhat-linux) of Thu May 6 1999 on javabench5.watson.ibm.com configured using `configure i686-redhat-linux --with-gcc --cflags=-O6 --with-gnu-make --dynamic --with-x11=yes --with-xpm --with-xface --with-database=gnudbm --with-socks' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I set up xemacs as in the intructions, except for one thing. In the file config.h I had to change all the occurences of Rconnect, Rbind, etc (for the socks stuff) to SOCKSconnect, SOCKSbind, etc. This is because I was using socks5 instead of socks4. I also had to include -lsocks5 in the link portion of the main Makefile (src/Makefile) I downloaded the sumo tar file and installed it as indicated in the instructions. I then set up the following .emacs file from the option menu for the root user: (custom-set-variables '(efs-remote-shell-takes-user t) '(socks-server (quote ("Default server" "socks2.watson.ibm.com" 1080 4))) '(efs-ftp-program-name "/usr/local/bin/rftp")) (custom-set-faces) rftp is just a socksofied ftp program from socks version 5. I then (as root) went into the the Options menu, went to Manage Packages, "Add download site" added the two top-most sites (xemacs.org and cso.uiuc.edu) and then selected "update install packages"... after finally connecting to the site ( i think it also went as far as succsessfully changing into the proper directory), xemacs promptly crashed. The crash message is included below followed by the C stack backtrace: Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. Please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org&#39;. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/local/bin/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: popup-dialog-box(("Package-get entries not PGP signed, continue? " ["Yes" yes t] ["No" no t] nil ["Cancel" abort t])) # bind (echo-keystrokes event prompt) yes-or-no-p-dialog-box("Package-get entries not PGP signed, continue? ") # bind (prompt) yes-or-no-p("Package-get entries not PGP signed, continue? ") # (unwind-protect ...) # bind (content-beg content-end beg end buf) package-get-update-base-from-buffer(#<buffer "*package database*">) # (unwind-protect ...) # (unwind-protect ...) # bind (buf force-current db-file) package-get-update-base(nil t) # bind (force-current) package-get-require-base(t) #<compiled-function nil "...(8)" [package-get-require-base t exit (mapcar #<compiled-function ... "...(14)" ... 4> packages-package-list)] 2 ("/usr/local/lib/xemacs-21.0-b67/lisp/package-get.elc" . 13956) nil>() call-interactively(package-get-update-all) # (condition-case ... . error) # (catch top-level ...) Here is the C stack backtrace: #0 0x40392811 in kill () from /lib/libc.so.6 #1 0x80afd55 in fatal_error_signal () #2 0xbfffe4f4 in ?? () #3 0x4010482e in XmProcessTraversal () from /usr/X11R6/lib/libXm.so.2 #4 0x81c117d in make_dialog () #5 0x81c1645 in xm_create_dialog () #6 0x81beac3 in instantiate_widget_instance () #7 0x81beb8c in lw_make_widget () #8 0x81bf43b in lw_create_widget () #9 0x80cf288 in x_popup_dialog_box () #10 0x80c5da9 in Fpopup_dialog_box () #11 0x80b55da in funcall_recording_as () #12 0x80b99e7 in Ffuncall () #13 0x808caf6 in Fbyte_code () #14 0x80b6764 in funcall_lambda () #15 0x80b5742 in funcall_recording_as () #16 0x80b99e7 in Ffuncall () #17 0x808caf6 in Fbyte_code () #18 0x80b6764 in funcall_lambda () #19 0x80b5742 in funcall_recording_as () #20 0x80b99e7 in Ffuncall () #21 0x808caf6 in Fbyte_code () #22 0x80b6764 in funcall_lambda () #23 0x80b5742 in funcall_recording_as () #24 0x80b99e7 in Ffuncall () #25 0x808caf6 in Fbyte_code () #26 0x80b6764 in funcall_lambda () #27 0x80b5742 in funcall_recording_as () #28 0x80b99e7 in Ffuncall () #29 0x808caf6 in Fbyte_code () #30 0x80b6764 in funcall_lambda () #31 0x80b5742 in funcall_recording_as () #32 0x80b99e7 in Ffuncall () #33 0x808caf6 in Fbyte_code () #34 0x80b6764 in funcall_lambda () #35 0x80b5742 in funcall_recording_as () #36 0x80b8c2c in apply1 () #37 0x808e3e3 in Fcall_interactively () #38 0x80b54e2 in funcall_recording_as () #39 0x80b8cb9 in call1 () #40 0x80e7d91 in execute_command_event () #41 0x80e8b2d in Fdispatch_event () #42 0x80952c3 in Fcommand_loop_1 () #43 0x80954c1 in command_loop_1 () #44 0x80b29b7 in condition_case_1 () #45 0x809559c in command_loop_2 () #46 0x80b9699 in internal_catch () #47 0x80949d3 in initial_command_loop () #48 0x80ae673 in xemacs_21_0_b67_i686_redhat_linux () #49 0x80aff5d in main () Hope that helps... -- Eugene Gluzberg, IBM T.J. Watson Research Center, Java Server Performance (JASPER) Group Phone 914-784-7345, T/L 863-7345 Fax 914-784-6201, T/L Fax 863-6201 gluzberg(a)watson.ibm.com