Re: Debugging 64bit xemacs (beta, latest cvs) on sparc64 (Sun T1000)

Hi Malcolm, Bad news I'm afraid. After further testing, I can get the patched xemacs to crash very easily, just by scrolling around with some ruby code. It is never exactly repeatable, which makes things a lot more difficult to nail down, but I can always get it to crash within a few 10s of seconds. :( andrew＠spawn1 xemacs-21.5-work $ cvs -q diff Index: configure =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/configure,v retrieving revision 1.291 diff -r1.291 configure 4393c4393 < sparc-*-* ) machine=sparc ;; --- Index: configure.ac =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/configure.ac,v retrieving revision 1.54 diff -r1.54 configure.ac 1287c1287 < sparc-*-* ) machine=sparc ;; --- andrew＠spawn1 xemacs-21.5-work $ xemacs --version XEmacs 21.5 (beta27) "fiddleheads" (+CVS-20070101) [Lucid] (sparc64-unknown-linux) of Tue Jan 2 2007 on spawn1.secure andrew＠spawn1 xemacs-21.5-work $ Typical crash: Lisp backtrace follows: # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # bind (print-message-label) display-error((end-of-buffer) t) # bind (etype debug-on-error inhibit-quit error-object) command-error((end-of-buffer)) # (catch top-level ...) Segmentation fault Everything else works peachy on this pure 64bit distro; only xemacs exhibits any problems. Not a high priority I guess since I am probably the only one building a 64bit version on sparc64, but I can give ssh access to a machine setup ready for debugging if it would help. Best, Andrew Walrond Malcolm Purvis wrote: _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta