RE: Repeatable crash on Solaris, with recipe

Tested your recipe on 21.4.8 built from the tarballs with Sun Workshop 6 update 1 on Solaris 2.7 results in an (apparently) hung editor. It's not consuming any noticeable quantity of CPU cycles and I can interrupt it with C-g and break out of whatever it thinks is going on. Hmmm, for me it seems to hang on the C-x h, actually. If I try to do M-x or M-: (or a variety of other things but a C-g for that matter) after the C-x h, I get no response from the editor. This seems to start with only 3236 lines of your test pattern in the buffer. I'm not sure at this point whether I have helped clarify or confused the issue :-/ Looks like I'm hitting a limit of some kind, but whether OS or XEmacs I'm not sure. Other than the fact it doesn't work, it seems fairly well behaved though, I didn't crash at all while narrowing down the buffer size. Regards, Jim -----Original Message----- From: Raymond Toy [mailto:toy＠rtp.ericsson.se] Sent: Monday, May 20, 2002 5:11 PM To: XEmacs Developers Cc: Benjamin P. Wing Subject: Repeatable crash on Solaris, with recipe I found a repeatable crash on Solaris with the following recipe. This is 21.5-b6 built from a full tarball using gcc 3.0.4 on Solaris 2.7. Start xemacs -vanilla. Evaluate the following function (defun foo (n) (dotimes (k n) (insert-string "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAA\n"))) That's a string of 80 A's but that shouldn't really matter. It's the size of the buffer that counts. In some buffer, M-: (foo 30000). Then do M-x text-mode. Then C-x h to mark the whole buffer. Finally, C-w to kill it. This crashes xemacs. The Lisp backtrace is: Lisp backtrace follows: # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # bind (undo-high-threshold tail verbose end start) kill-region(1 2430001 1) # bind (command-debug-status) call-interactively(kill-region) # (condition-case ... . error) # (catch top-level ...) Abort (core dumped) The C backtrace is corrupted, but I get: #0 0xfec1a1f0 in _libc_kill () from /usr/lib/libc.so.1 #1 0xa76d0 in fatal_error_signal (sig=6) at /apps/public/XEmacs/src/xemacs-21.5.6/src/emacs.c:3358 #2 <signal handler called> #3 0xfec1a1f0 in _libc_kill () from /usr/lib/libc.so.1 #4 0xfebb959c in abort () from /usr/lib/libc.so.1 #5 0xa860c in zero_out_command_line_status_vars () at /apps/public/XEmacs/src/xemacs-21.5.6/src/emacs.c:4189 This is starting to bite me at least once a day, especially in GNUS when someone sends me some huge Word attachment. I'll try to figure this out, but I need some guidance on what to look for. Thanks, Ray