Subject: pkg/15561: pkgsrc xemacs dumps core on delete-window from wm
To: None <>
From: None <>
List: netbsd-bugs
Date: 02/10/2002 05:31:42
>Number:         15561
>Category:       pkg
>Synopsis:       pkgsrc xemacs dumps core on delete-window from wm
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 09 20:32:00 PST 2002
>Originator:     Matthias Buelow
>Release:        NetBSD 1.5.3_ALPHA
System: NetBSD 1.5.3_ALPHA NetBSD 1.5.3_ALPHA (ALTAIR) #3: Mon Jan 21 02:21:16 CET 2002 i386
Architecture: i386
Machine: i386


	xemacs 21.1.14, build from 2002/01/20 pkgsrc.
	If you quit xemacs by sending a delete window message from
	a typical window manager function (like often invoked
	via window manager title-bar decoration buttons), xemacs
	triggers a segmentation violation and exits ungracefully.
	This has been verified on the windowmaker and twm window
	Xemacs spits the following to stderr:

	Fatal error (11).
	Your files have been auto-saved.
	Use `M-x recover-session' to recover them.

	If you have access to the PROBLEMS file that came with your
	version of XEmacs, please check to see if your crash is described
	there, as there may be a workaround available.
	Otherwise, 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 `'.
	*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 /usr/pkg/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:

	  # bind (arg)
	  delete-frame(#<x-frame "emacs" 0xb85> t)
	  eval((delete-frame #<x-frame "emacs" 0xb85> t))
	  # (condition-case ... . error)
	  # (catch top-level ...)

	[2] + Memory fault         xemacs  (core dumped)

	xemacs wasn't build with symbols, so the gdb traceback
	is not very informative:

	#0  0x485890e3 in kill ()
	#1  0x807240b in dladdr ()
	#2  0xbfbfdfdc in ?? ()
	#3  0x483ff20e in XtGetValues ()
	#4  0x811e978 in alarm ()
	#5  0x80c0055 in tgoto ()
	#6  0x8068bca in dladdr ()
	#7  0x8063858 in dladdr ()
	#8  0x807395f in dladdr ()
	#9  0x8077ccd in dladdr ()
	#10 0x8077e5d in dladdr ()
	#11 0x805a17a in dladdr ()
	#12 0x8078713 in dladdr ()
	#13 0x8077e21 in dladdr ()
	#14 0x8077e5d in dladdr ()
	#15 0x8078ba3 in dladdr ()
	#16 0x806377e in dladdr ()
	#17 0x8068ad0 in dladdr ()
	#18 0x80bfdc4 in tgoto ()
	#19 0x80c0502 in tgoto ()
	#20 0x8077804 in dladdr ()
	#21 0x8077ccd in dladdr ()
	#22 0x8077e5d in dladdr ()
	---Type <return> to continue, or q <return> to quit---
	#23 0x8078bf4 in dladdr ()
	#24 0x80a3885 in tgoto ()
	#25 0x80a3d50 in tgoto ()
	#26 0x8061c62 in dladdr ()
	#27 0x8061aec in dladdr ()
	#28 0x8075de6 in dladdr ()
	#29 0x80616f4 in dladdr ()
	#30 0x8061710 in dladdr ()
	#31 0x8075b59 in dladdr ()
	#32 0x8061878 in dladdr ()
	#33 0x807321a in dladdr ()
	#34 0x80738af in dladdr ()
	#35 0x804efb9 in XMapRaised ()

	I have not yet verified if this also occurs on other
	operating systems.


	Exit xemacs by selecting "Close" or "Delete" from your
	window manager's menu or by hitting the appropriate button
	on the decoration.  It can be reproduced with twm, which
	is shipped with NetBSD's X11 by default.