The crash I'm getting is occurring in a call to Gpm_Open, but only when XEmacs is run inside an xterm. When run on the Linux console the splash screen comes up. When I build without GPM everything is fine. I'm not done poking around to get more information, but if everyone with access to a Linux machine for testing could do some checking of this it would be helpful. In particular it would be good to know if this is only a glibc-2.0.1xx problem, or something else specific to my development environment, or if it's Mule -vs- no-Mule, etc. Thanks for any info. $ gdb src/xemacs GNU gdb 4.16.85 Copyright 1997 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-linux-gnu"... (gdb) run -nw Starting program: /devel/xemacs/build20/mule/src/xemacs -nw Program received signal SIGSEGV, Segmentation fault. 0x403bd051 in _IO_fflush (fp=0x40451100) at iofflush.c:41 41 result = _IO_SYNC (fp) ? EOF : 0; (gdb) where #0 0x403bd051 in _IO_fflush (fp=0x40451100) at iofflush.c:41 #1 0x402da5cd in Gpm_Open () #2 0xd0000 in ?? () Cannot access memory at address 0x1000d. (gdb) quit The configuration I'm testing is Linux 2.2.0-pre4/2.2.0-pre5-ac1, glibc-2.0.108 and glibc-2.0.109, pgcc/egcs-1.1.1, XFree86-3.3.3 and gpm-1.13. uname -a: Linux demeter.xemacs.org 2.2.0-pre5-ac1 #2 SMP Thu Jan 7 02:53:22 PST 1999 i686 unknown /devel/xemacs/xemacs-21.0/configure '--cflags=-g' '--with-mule=yes' '--with-dialogs=athena3d' '--with-scrollbars=athena3d' '--use-union-type=yes' '--with-xim=xlib' '--with-xfs' '--mail-locking=file' '--extra-verbose=no' '--srcdir=/devel/xemacs/xemacs-21.0' '--with-gnu-make' '--with-gpm=no' XEmacs 21.0-b62 "Pyrenean" configured for `i686-pc-linux'. Where should the build process find the source code? /devel/xemacs/xemacs-21.0 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) 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/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for proper session-management. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. Using Lisp_Objects with minimal tagbits. 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: ---------------------------------------------------------