Hi Alexander, please specify the exact configure options you tried. Based on that information you might actually get some help from the XEmacs developers. Have you tried --pdump? Try searching http://list-archive.xemacs.org/xemacs-buildreports/ and http://list-archive.xemacs.org/xemacs-beta/ Here's all I found: http://list-archive.xemacs.org/cgi-bin/wilma_glimpse/xemacs-build-reports... http://list-archive.xemacs.org/cgi-bin/wilma_glimpse/xemacs-beta?query=bi... Best regards, Adrian Alexander> first, what happened: Alexander> $xemacs Alexander> Fatal error (11). Alexander> Your files have been auto-saved. Alexander> Use `M-x recover-session' to recover them. Alexander> If you have access to the PROBLEMS file that came with your Alexander> version of XEmacs, please check to see if your crash is described Alexander> there, as there may be a workaround available. Alexander> Otherwise, please report this bug by running the send-pr Alexander> script included with XEmacs, or selecting `Send Bug Report' Alexander> from the help menu. Alexander> As a last resort send ordinary email to `crashes(a)xemacs.org&#39;. Alexander> *MAKE SURE* to include the information in the command Alexander> M-x describe-installation. Alexander> If at all possible, *please* try to obtain a C stack backtrace; Alexander> it will help us immensely in determining what went wrong. Alexander> To do this, locate the core file that was produced as a result Alexander> of this crash (it's usually called `core' and is located in the Alexander> directory in which you started the editor, or maybe in your home Alexander> directory), and type Alexander> gdb /usr/local/bin/xemacs core Alexander> then type `where' when the debugger prompt comes up. Alexander> (If you don't have GDB on your system, you might have DBX, Alexander> or XDB, or SDB. A similar procedure should work for all of Alexander> these. Ask your system administrator if you need more help.) Alexander> Lisp backtrace follows: Alexander> # bind (frame-being-created) Alexander> make-frame(nil #<x-device on ":0.0" 0x1ba8>) Alexander> frame-initialize() Alexander> # bind (debugger debug-on-error command-line-args-left) Alexander> command-line() Alexander> # (condition-case ... . ((t (byte-code " Â?" ... 1)))) Alexander> # bind (error-data) Alexander> normal-top-level() Alexander> # (condition-case ... . error) Alexander> # (catch top-level ...) Alexander> Speicherzugriffsfehler Alexander> ok, i tried to complie different versions of emacs. tried to use different configure/compile options. well, i failed. Alexander> i'm running suse linux and i am quite confused why it doesnt run. well, that's from me.. *shrugs helplessly* Alexander> ________________________________________________________________ Alexander> Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Alexander> Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13 -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

vin> This is probably a result of your loader rearranging the vin> segments, messing up the dumped image. The easiest fix is to vin> configure '--pdump'. Search for 'Lecter' in the PROBLEMS vin> file for more details. That will only be available in 21.4 and above. I recommend the latest 21.4. 21.1 is "lame duck" (which means we will shortly promote 21.4 to "stable", and so no more 21.1 releases, and although we'll answer 21.1 mail, our response will normally be limited to "upgrade to 21.4"). -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py