Re: <no subject>

first, what happened: $xemacs 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 /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: # bind (frame-being-created) make-frame(nil #<x-device on ":0.0" 0x1ba8>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " Â?" ... 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Speicherzugriffsfehler ok, i tried to complie different versions of emacs. tried to use different configure/compile options. well, i failed. i'm running suse linux and i am quite confused why it doesnt run. well, that's from me.. *shrugs helplessly* ________________________________________________________________ Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13