xemacs crash
Adrian Aichner
adrian at xemacs.org
Mon May 10 08:56:00 EDT 2004
Paul <pharris2 at umbc.edu> writes:
> This is an error report that occurred when I decided not to exit a
> file, but then it crashed. The rest of the xemacs sessions I had up
Paul, please use
Help->Send Bug Report...
or
M-x report-emacs-bug
as suggested in
http://www.xemacs.org/Debug/index.html
This will tell us enough about your XEmacs installation so that we
should be able to help you.
If XEmacs does not build or start up, please send any version and
configuration information you have to xemacs-beta at xemacs.org with any
mailer as plain text (MIME attachments are OK, please don't send HTML
mail).
On linux type
ulimit -c unlimited
in the shell before starting XEmacs from it, else you might not get a
core file.
Best regards,
Adrian
> stayed up. I looked for a core, but coiuldnt' find one. I'm assuming
> thats cuz it aborted instead of segfaulting. If not it could be
> because someone told me how to make it so that none of my programs
> would dump cores, just segfault and automatically delete the core.
>
> thanks
>
>
>
> Fatal error (6).
> 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 at xemacs.org'.
> *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:
> next-command-event()
> byte-code("..." [popup-dialog-box dbox dispatch-event
> next-command-event] 2)
> # (catch result ...)
> # bind (dbox contents position)
> get-dialog-box-response(#<misc-user-event (eval (delete-frame
> #<x-frame "emacs" 0x23f2> t))> ("Save file
> /afs/umbc.edu/users/p/h/pharris2/home/cmsc341/proj5/IntervalHeap.C?
> " ("Yes" . act) ("No" . skip) ("Yes All" . automatic) ("No All"
> . exit) ("Cancel" . quit) ("Display The Current Buffer"
> . [#<compiled-function ... "...(18)" ... 2>])))
> # (unwind-protect ...)
> # bind (next def elt char prompt map mouse-event user-keys actions
> # no-cursor-in-echo-area action-alist help list actor prompter)
> map-y-or-n-p(#<compiled-function (buffer) "...(132)"
> [buffer-modified-p buffer buffer-base-buffer symbol-value-in-buffer
> save-buffers-skip buffer-file-name exiting buffer-offer-save
> buffer-size 0 arg t switch-buffer one-window-p delete-other-windows
> switched switch-to-buffer format "Save file %s? " "Save buffer %s? "
> buffer-name] 4> #<compiled-function (buffer) "...(14)" [buffer nil
> (save-buffer) (...)] 3> (#<buffer "IntervalHeap.C"> #<buffer
> "IntervalHeap.H"> #<buffer "*scratch*"> #<buffer " *Minibuf-0*">
> #<buffer " *Echo Area*"> #<buffer " *pixmap conversion*"> #<buffer "
> *load*"> #<buffer " *string-as-buffer-contents*"> #<buffer "
> *Message-Log*">) ("buffer" "buffers" "save") ((?\^R
> #<compiled-function ... "...(18)" ... 2> "display the current
> buffer")))
> # bind (switched switch-buffer exiting arg)
> save-some-buffers-1(nil t t)
> # (unwind-protect ...)
> # (unwind-protect ...)
> # bind (exiting arg)
> save-some-buffers(nil t)
> # bind (arg)
> save-buffers-kill-emacs()
> delete-frame(#<x-frame "emacs" 0x23f2> t)
> eval((delete-frame #<x-frame "emacs" 0x23f2> t))
> # (condition-case ... . error)
> # (catch top-level ...)
> [1] Aborted xemacs IntervalHeap.C IntervalHeap.H
>
>
--
Adrian Aichner
mailto:adrian at xemacs.org
http://www.xemacs.org/
More information about the XEmacs-Beta
mailing list