Crashes running emacs or xemacs: segmentation fault

[Matthew Johnson]

Although your instructions say to find 'core' and run it under gdb, the 
only 'core' files I can find are clearly not from emacs or xemacs. So I 
cannot give you that.

In fact, I really do suspect that the root cause of this problem has 
nothing to do with emacs or xemacs, but everything to do with Cygwin/X. 
Perhaps you can come up with something helpful with that information.

The crash message in xterm is:

 $ xemacs applications/consoleapp/consoleapp.cpp
Warning: XtRemoveGrab asked to remove a widget not on the list
Warning: XtRemoveGrab asked to remove a widget not on the list

Fatal error (11).

Your files have been auto-saved.
Use `M-x recover-session' to recover them.

Your version of XEmacs was distributed with a PROBLEMS file that  may 
describe
your crash, and with luck a workaround.  Please check it first, but do 
report
the crash anyway.  Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu.  If necessary, send
ordinary email to `crashes at xemacs.org'.  *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.

*Please* try *hard* to obtain a C stack backtrace; without it, we are 
unlikely
to be able to analyze the problem.  Locate the core file produced as a 
result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type

  gdb /usr/bin/xemacs core

then type `where' at the debugger prompt.  No GDB on your system?  You may
have DBX, or XDB, or SDB.  (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.

Lisp backtrace follows:

  kill-emacs()
  # bind (arg)
  save-buffers-kill-emacs(nil)
  # bind (command-debug-status)
  call-interactively(save-buffers-kill-emacs)
  # (condition-case ... . error)
  # (catch top-level ...)
Segmentation fault


And although I get errors about clipboard in X while running startx, I 
was able to use X's cut-and-paste from xterm to get the above into my 
WinXP email client!

Now re-entering the command line that invoked xemacs and invoking 
'describe-installation' I get:
uname -a: CYGWIN_NT-5.0 summer 1.5.7(0.109/3/2) 2004-01-30 19:32 i686 
unknown unknown Cygwin

/usr/src/xemacs-21.4.15/configure  '--pdump' 
'--srcdir=/usr/src/xemacs-21.4.15' '--prefix=/usr' 
'--datadir=/usr/share' '--statedir=/var' '--libdir=/usr/lib' 
'--infodir=/usr/share/xemacs-21.4.15/info' 
'--mandir=/usr/share/man/man1' 
'--package-path=/usr/local/share/xemacs/site-packages:/usr/share/xemacs/site-packages:/usr/share/xemacs/xemacs-packages:/usr/share/xemacs/mule-packages' 
'--with-mule' '--with_file_coding=yes' '--with_msw=yes' 
'--with-modules=no' '--with-dialogs=motif' '--with-widgets=motif'


XEmacs 21.4.15 "Security Through Obscurity" configured for `i686-pc-cygwin'.


Compilation / Installation:
  Source code location:              /usr/src/xemacs-21.4.15
  Installation prefix:               /usr
  Operating system description file: `s/cygwin32.h'
  Machine description file:          `m/intel386.h'
  Compiler:                          gcc -g -O3 -Wall -Wno-switch 
-Winline -Wmissing-prototypes -Wsign-compare -fno-strict-aliasing 
-Wshadow -Wpointer-arith
  Compiler version:                  gcc (GCC) 3.3.1 (cygming special)
  Compiler specs file:               
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/specs
  Relocating allocator for buffers:  no
  GNU version of malloc:             yes
  libc:                              system-provided libc on i686-pc-cygwin

Window System:
  Compiling in support for the Microsoft window system.
  Compiling in support for the X window system:
    - X Windows headers location:                 /usr/X11/include
    - X Windows libraries location:               /usr/X11R6/lib
    - Handling WM_COMMAND properly.
  Compiling in support for Motif.
    - Using LessTif implementation.
  *WARNING*  Many versions of Motif are buggy, requiring workarounds.
             You are likely to experience slow redisplay.
             You may need to install vendor patches to Motif.
             See PROBLEMS for more information.
  Using Lucid menubars.
  Using Lucid scrollbars.
  Using Motif dialog boxes.
  Using Motif native widgets.

TTY:
  Compiling in support for ncurses.

Images:
  Compiling in support for GIF  images (builtin).
  Compiling in support for XPM  images.
  Compiling in support for PNG  images.
  Compiling in support for JPEG images.
  Compiling in support for TIFF images.
  Compiling in support for X-Face message headers.

Sound:
  Compiling in support for sound (native).

Databases:
  Compiling in support for Berkeley database.
  Compiling in support for LDAP.
  Compiling in support for PostgreSQL.
    - Using PostgreSQL header file:  libpq-fe.h
    - Using PostgreSQL V7 bindings.

Internationalization:
  Compiling in support for Mule (multi-lingual Emacs).
  Compiling in support for file coding.
  Compiling in support for XIM (X11R5+ I18N input method).
    - Using raw Xlib to provide XIM support.

Mail:
  Compiling in support for POP mail retrieval.

Other Features:
  Inhibiting IPv6 canonicalization at startup.
  Using the new portable dumper.

And as you can see, copy-and-paste worked from inside xemacs too, even 
though I regularly get the error messages:

winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.

as the final messages during startx.

Finally, no, alas, I don't remember what I was doing when the error occured.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjohnson.vcf
Type: text/x-vcard
Size: 326 bytes
Desc: not available
Url : http://calypso.tux.org/pipermail/xemacs-beta/attachments/20050308/fb5ea8a8/attachment.vcf