Xemacs, I originally sent e-mail to Adrian.aichner(a)t-online.de. Adrian said to send it here. All that is needed to recreate the error, is to xemacs any C file and once it is loaded just ask to "File Revert Buffer" and you get a core dump. Here is the C stack Backtrace results. It doesn't look like much to me but I have never looked at one before. I hope this helps, Tim Morauske ***************************************************** $ xemacs te.c& [1] 6657 tim_apex /home/morauske $ Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. If you have access to the PROBLEMS file that came with your version of XEmacs, please check to see if your crash is described there, as there may be a workaround available. Otherwise, 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 /opt/xemacs/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(("Revert buffer from file /home/morauske/te.c? " ["Yes" yes t] ["No" no t] nil ["Cancel" abort t])) # bind (echo-keystrokes event) # (unwind-protect ...) # bind (ssf27888 prompt) yes-or-no-p-dialog-box("Revert buffer from file /home/morauske/te.c? ") # bind (prompt) yes-or-no-p("Revert buffer from file /home/morauske/te.c? ") # bind (file-name auto-save-p opoint preserve-modes noconfirm ignore-auto) #<compiled-function (&optional ignore-auto noconfirm preserve-modes) "...(261)" [revert-buffer-function ignore-auto noconfirm opoint recent-auto-s ave-p buffer-auto-save-file-name file-readable-p y-or-n-p "Buffer has been auto-saved recently. Revert from auto-save file? " auto-save-p buffer-fi le-name file-name error "Buffer does not seem to be associated with any file" buffer-modified-p nil found revert-without-query rx --dolist-temp--278 93 string-match t yes-or-no-p format "Revert buffer from file %s? " run-hooks before-revert-hook verify-visited-file-modtime buffer-backed-up buffer -undo-list default-value after-revert-hook local-variable-p local-hook local-hook-p global-hook buffer-read-only revert-buffer-insert-file-contents- function file-exists-p "File %s no longer exists!" unlock-buffer insert-file-contents after-find-file preserve-modes set-default revert-buffer-inter nal-hook make-local-variable kill-local-variable] 7 813690 (list (not current-prefix-arg))>(t) call-interactively(revert-buffer) # (condition-case ... . error) # (catch top-level ...) [1] + Memory fault(coredump) xemacs te.c& tim_apex /home/morauske $ gdb /opt/xemacs/bin/xemacs core Wildebeest is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for Wildebeest; type "show warranty" for details. Hewlett-Packard Wildebeest 1.0 (based on GDB 4.16) (built for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00) Copyright 1996, 1997 Free Software Foundation, Inc...(no debugging symbols found)... Core was generated by `xemacs-21.1.14'. Program terminated with signal 11, Segmentation fault. Unable to find __dld_flags symbol in object file. #0 0xc01f4000 in ?? () #0 0xc01f4000 in ?? () (gdb) where #0 0xc01f4000 in ?? () #1 0x9e0b4 in ?? () Cannot access memory at address 0xffffff6c. (gdb) ***************************************************** Hi Tim! It's actually part of the error message you got: 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 You'll have to substitute HP-UX's equivalent of a C debugger, and the correct path to the xemacs executable producing the core file. Hope this helps, Adrian TIM> Adrian, TIM> What is the process for getting a C stack backtrace that you said you TIM> needed? TIM> Tim Morauske TIM> -----Original Message----- TIM> From: Adrian.Aichner(a)t-online.de [mailto:Adrian.Aichner＠t-online.de] TIM> Sent: Friday, September 28, 2001 2:54 PM TIM> To: MORAUSKE,TIM (HP-Boise,ex1) TIM> Cc: XEmacs Beta List TIM> Subject: Re: xemacs Revert Buffer on HP-UX 11.0 causes core dump TIM> Hi Tim, TIM> could you please send us (xemacs-beta(a)xemacs.org) a C stack backtrace TIM> as recommended below? TIM> You may want to send the information with TIM> M-x report-xemacs-bug TIM> or TIM> M-x report-emacs-bug TIM> depending on the availability and version of the net-utils package. TIM> If you have a recent version of net-utils installed (which I TIM> recommend) it will tell us important facts about your XEmacs TIM> installation. TIM> Best regards, TIM> 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 TIM> 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 TIM> /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> ") TIM> # bind (file-name auto-save-p opoint preserve-modes noconfirm TIM> ignore-auto) TIM> #<compiled-function (&optional ignore-auto noconfirm TIM> 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 TIM> 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 TIM> file" TIM> buffer-modified-p nil found revert-without-query rx TIM> --dolist-temp--27893 str TIM> ing-match t yes-or-no-p format "Revert buffer from file %s? " TIM> 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 TIM> local-hook-p TIM> global-hook buffer-read-only TIM> revert-buffer-insert-file-contents-function f TIM> ile-exists-p "File %s no longer exists!" unlock-buffer TIM> insert-file-contents TIM> after-find-file preserve-modes set-default TIM> 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 TIM> license TIM> ./configure TIM> XEmacs 21.1.14 "Cuyahoga Valley" configured for TIM> `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? TIM> /opt/xemacs TIM> What operating system and machine description files should XEmacs TIM> use? TIM> `s/hpux11.h' and `m/hp800.h' TIM> What compiler should XEmacs be built with? TIM> /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? TIM> /usr/dt/include TIM> /usr/include/X11R6 /usr/contrib/X11R6/include TIM> Where do we find X Windows libraries? TIM> /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. TIM> -- TIM> Adrian Aichner TIM> mailto:adrian＠xemacs.org TIM> http://www.xemacs.org/ -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/