Re: xemacs Revert Buffer on HP-UX 11.0 causes core dump

Hi Tim, could you please send us (xemacs-beta(a)xemacs.org) a C stack backtrace as recommended below? You may want to send the information with M-x report-xemacs-bug or M-x report-emacs-bug depending on the availability and version of the net-utils package. If you have a recent version of net-utils installed (which I recommend) it will tell us important facts about your XEmacs installation. Best regards, Adrian TIM> Adrian, TIM> I just got a new HP C3600 system and installed xemacs 21.1.14 TIM> on it. I also have the Revert buffer problem that you TIM> replied to Peter Mours on 16 May 2001. TIM> You asked for more information. What would you like. Here TIM> is what was outputted to the screen. All I had to do is just TIM> do a TIM> I also tried to open a file and choose revert prior to any TIM> changes and also got a core dump. TIM> I also had loaded xemacs 21.1.9 on my system and it also core TIM> dumps when you revert your buffer. TIM> Any help would be greatly appreciated. TIM> Thanks TIM> Tim TIM> At the end of this file is the output for the question that TIM> you asked Peter Mours. "Send in the information obtained by TIM> M-x describe-installation" TIM> ################# Screen output for a file that was modified but then TIM> reverted ############################ TIM> Fatal error (11). TIM> Your files have been auto-saved. TIM> Use `M-x recover-session' to recover them. TIM> If you have access to the PROBLEMS file that came with your TIM> version of XEmacs, please check to see if your crash is described TIM> there, as there may be a workaround available. TIM> Otherwise, please report this bug by running the send-pr TIM> script included with XEmacs, or selecting `Send Bug Report' TIM> from the help menu. TIM> As a last resort send ordinary email to `crashes(a)xemacs.org&#39;. TIM> *MAKE SURE* to include the information in the command TIM> M-x describe-installation. TIM> If at all possible, *please* try to obtain a C stack backtrace; TIM> it will help us immensely in determining what went wrong. TIM> To do this, locate the core file that was produced as a result TIM> of this crash (it's usually called `core' and is located in the TIM> directory in which you started the editor, or maybe in your home TIM> directory), and type TIM> gdb /opt/xemacs/bin/xemacs core TIM> then type `where' when the debugger prompt comes up. TIM> (If you don't have GDB on your system, you might have DBX, TIM> or XDB, or SDB. A similar procedure should work for all of TIM> these. Ask your system administrator if you need more help.) TIM> Lisp backtrace follows: TIM> popup-dialog-box(("Revert buffer from file /home/morauske/tcl_jemBgm.c? " TIM> ["Yes" yes t] ["No" no t] nil ["Cancel" abort t])) TIM> # bind (echo-keystrokes event) TIM> # (unwind-protect ...) TIM> # bind (ssf27888 prompt) TIM> yes-or-no-p-dialog-box("Revert buffer from file TIM> /home/morauske/tcl_jemBgm.c? ") TIM> # bind (prompt) TIM> yes-or-no-p("Revert buffer from file /home/morauske/tcl_jemBgm.c? ") TIM> # bind (file-name auto-save-p opoint preserve-modes noconfirm ignore-auto) TIM> #<compiled-function (&optional ignore-auto noconfirm preserve-modes) TIM> "...(261)" [revert-buffer-function ignore-auto noconfirm opoint TIM> recent-auto-sav TIM> e-p buffer-auto-save-file-name file-readable-p y-or-n-p "Buffer has been TIM> auto-saved recently. Revert from auto-save file? " auto-save-p TIM> buffer-file-n TIM> ame file-name error "Buffer does not seem to be associated with any file" TIM> buffer-modified-p nil found revert-without-query rx --dolist-temp--27893 str TIM> ing-match t yes-or-no-p format "Revert buffer from file %s? " run-hooks TIM> before-revert-hook verify-visited-file-modtime buffer-backed-up TIM> buffer-undo-li TIM> st default-value after-revert-hook local-variable-p local-hook local-hook-p TIM> global-hook buffer-read-only revert-buffer-insert-file-contents-function f TIM> ile-exists-p "File %s no longer exists!" unlock-buffer insert-file-contents TIM> after-find-file preserve-modes set-default revert-buffer-internal-hook mak TIM> e-local-variable kill-local-variable] 7 813690 (list (not TIM> current-prefix-arg))>(t) TIM> call-interactively(revert-buffer) TIM> # (condition-case ... . error) TIM> # (catch top-level ...) TIM> Memory fault(coredump) TIM> ##### M-x ############## TIM> uname -a: HP-UX quioch B.11.00 A 9000/780 2012209406 two-user license TIM> ./configure TIM> XEmacs 21.1.14 "Cuyahoga Valley" configured for `hppa1.1-hp-hpux11.00'. TIM> Where should the build process find the source code? TIM> /opt/bintmp/xemacs-21.1.14 TIM> What installation prefix should install use? /opt/xemacs TIM> What operating system and machine description files should XEmacs use? TIM> `s/hpux11.h' and `m/hp800.h' TIM> What compiler should XEmacs be built with? /opt/gcc/bin/gcc TIM> -Wall -Wno-switch TIM> Should XEmacs use the GNU version of malloc? yes TIM> Should XEmacs use the relocating allocator for buffers? yes TIM> What window system should XEmacs use? x11 TIM> Where do we find X Windows header files? /usr/dt/include TIM> /usr/include/X11R6 /usr/contrib/X11R6/include TIM> Where do we find X Windows libraries? /usr/dt/lib TIM> /usr/lib/X11R6 /usr/contrib/X11R6/lib TIM> Compiling in support for XPM images. TIM> Compiling in support for PNG image handling. TIM> Compiling in support for (builtin) GIF image handling. TIM> Compiling in support for DBM. TIM> Compiling in support for ToolTalk. TIM> Compiling in support for proper session-management. TIM> Using Lucid menubars. TIM> Using Lucid scrollbars. TIM> Using Motif dialog boxes. TIM> Compiling in DLL support. TIM> movemail will use "dot-locking" for locking mail spool files. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/