From xemacs-m  Mon Mar 24 18:14:58 1997
Received: from newman (root@newman.aventail.com [38.225.141.10])
	by xemacs.org (8.8.5/8.8.5) with SMTP id SAA22913
	for <xemacs-beta@xemacs.org>; Mon, 24 Mar 1997 18:14:54 -0600 (CST)
Received: from kramer.in.aventail.com.aventail.com (wmperry@kramer [192.168.1.12]) by newman (8.6.12/8.6.9) with SMTP id QAA13918 for <xemacs-beta@xemacs.org>; Mon, 24 Mar 1997 16:12:18 -0800
Date: Mon, 24 Mar 1997 16:12:18 -0800
Message-Id: <199703250012.QAA13918@newman>
From: "William M. Perry" <wmperry@aventail.com>
To: xemacs-beta@xemacs.org
Subject: UnixWare & b104
Errors-to: wmperry@aventail.com
Reply-to: wmperry@aventail.com
X-Face: O~Rn;(l][/-o1sALg4A@xpE:9-"'IR[%;,,!m7</SYF`{vYQ(&RI1&EiH[FvT;J}@f!4kfz
 x_!Y#=y{Uuj9GvUi=cPuajQ(Z42R[wE@{G,sn$qGr5g/wnb*"*ktI+,CD}1Z'wxrM2ag-r0p5I6\nA
 [WJopW_J.WY;

failed.  Works fine under TTY mode, but under X I get:

No creation function for widget type menubar
Fatal error (6).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.

Please report this bug to the address `crashes@xemacs.org'.
*MAKE SURE* to include as much configuration information as
possible; at the very least what OS and hardware you are running
on, and hopefully also what compiler and compiler options the
binary was compiled with, what options XEmacs was compiled with,
whether you are using a prebuilt binary from ftp.xemacs.org or
compiled XEmacs yourself for your system, etc.

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 XEmacs, or maybe in your home
directory), and type

  gdb /usr/local/src/xemacs-19.15-b104/src/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 (frame-being-created)
  make-frame(nil #<x-device on "kramer:0.0" 0x671>)
  frame-initialize()
  # bind (debugger debug-on-error command-line-args-left)
  command-line()
  # (unwind-protect ...)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)
ABORT instruction (core dumped)

