This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.0 "20 minutes to Nikko" [Lucid] (sparc-sun-solaris2.5.1) of Fri Apr 9 1999 on brabham configured using `configure --prefix=/app_share/xemacs/21.0.67 --with-jpeg=no' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I was editing a gnats PR from within xemacs when the crash happened. It was about the 10th consecutive one I had done, ie there were no problems with the prior ones. No core file was produced since I have disabled this. Here is the info I have: uname -a: SunOS brabham 5.5.1 Generic_103640-24 sun4m sparc SUNW,SPARCstation-20 ./configure '--prefix=/app_share/xemacs/21.0.67' '--with-jpeg=no' XEmacs 21.0-b67 "20 minutes to Nikko" configured for `sparc-sun-solaris2.5.1'. Where should the build process find the source code? /app_share/xemacs/src/xemacs-21.0.67 What installation prefix should install use? /app_share/xemacs/21.0.67 What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/dt/include /app/links/include Where do we find X Windows libraries? /usr/dt/lib /app/links/lib Runtime library search path: /usr/ccs/lib:/usr/dt/lib:/app/links/lib Compiling in support for XAUTH. Compiling in support for XPM images. -------------------------------------------------------------------- WARNING: Compiling without PNG image support. Reason: PNG library version and header file don't match! WARNING: You should strongly consider installing the PNG libraries. WARNING: Otherwise certain images and glyphs may not display. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- Compiling in support for (builtin) GIF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- ulu~: Fatal error: assertion failed, file lstream.h, line 33, RECORD_TYPEP (_obj, lrecord_lstream) || MARKED_RECORD_P (_obj) 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(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 /app_share/xemacs/21.0.67/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: process-send-region(#<process " *file-pr--125871145" pid 8092 state:exit> 1 3794) # bind (process-environment proc) # (unwind-protect ...) # bind (buf inbuf proc-name proc-action proc-send-buffer args filep outfile sentinel proctype pr) gnats::start-background("bondi/17154" file gnats::handle-file-pr) gnats::file-pr-background() # (unwind-protect ...) # bind (buf result pr event process) gnats::handle-check-pr(#<process " *check-pr--116856671" pid 8090 state:exit> "finished\n") # (condition-case ... . error) # bind (inhibit-quit) # (unwind-protect ...) # (condition-case ... . error) # (catch top-level ...) Recent keystrokes: Recent messages (most recent first): irrelevant since crash occurred