Re: xlib6 and xemacs19

1997-06-12 Thread Elad Tsur
>I just installed several parts of the new XFree86 3.3 packages
>including xlib6.  xemacs will no longer start up.  The versions of
>packages are
[...]
> Is anyone else encountering this problem or is it something peculiar
> to my system?  The gory details are shown below.  I wanted to find out
> if this was reproducible on other systems before reporting it to
> xemacs.org

Yes, I also have this problem... There are already three bugreports on
this in bugs.debian.org. However I don't know if sombody have already
reported this to xemacs.org.

-- 
Elad Tsur


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


xlib6 and xemacs19

1997-06-10 Thread Douglas Bates
I just installed several parts of the new XFree86 3.3 packages
including xlib6.  xemacs will no longer start up.  The versions of
packages are
ii  xemacs1919.15-3XEmacs 19.15 editor and kitchen sink
ii  xemacs19-suppor 19.15-3Support files for XEmacs 19.15.
ii  xemacs19-suppor 19.15-3el library files for XEmacs 19.15.
ii  xlib6   3.3-1  Shared libraries required by X clients

Is anyone else encountering this problem or is it something peculiar
to my system?  The gory details are shown below.  I wanted to find out
if this was reproducible on other systems before reporting it to
xemacs.org

 $ xemacs

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

 Please report this bug to the address [EMAIL PROTECTED]'.
 *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/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:

 Segmentation fault (core dumped)
 $ gdb /usr/bin/xemacs core
 GDB is free software and you are welcome to 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.
 GDB 4.16 (i586-debian-linux), Copyright 1996 Free Software Foundation, Inc...
 (no debugging symbols found)...
 Core was generated by `xemacs'.
 Program terminated with signal 11, Segmentation fault.
 Reading symbols from /usr/X11R6/lib/Xaw3d/libXaw.so.6...
 (no debugging symbols found)...done.
 Reading symbols from /usr/X11R6/lib/libXpm.so.4...
 (no debugging symbols found)...done.
 Reading symbols from /usr/lib/libcompface.so.1...
 (no debugging symbols found)...done.
 Reading symbols from /usr/lib/libjpeg.so.6a...(no debugging symbols found)...
 done.
 Reading symbols from /usr/lib/libpng.so.1...(no debugging symbols found)...
 done.
 Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
 Reading symbols from /usr/X11R6/lib/libXmu.so.6...
 (no debugging symbols found)...done.
 Reading symbols from /usr/X11R6/lib/libXt.so.6...
 (no debugging symbols found)...done.
 Reading symbols from /usr/X11R6/lib/libSM.so.6...
 (no debugging symbols found)...done.
 Reading symbols from /usr/X11R6/lib/libICE.so.6...
 (no debugging symbols found)...done.
 Reading symbols from /usr/X11R6/lib/libXext.so.6...
 (no debugging symbols found)...done.
 Reading symbols from /usr/X11R6/lib/libX11.so.6...
 (no debugging symbols found)...done.
 Reading symbols from /lib/libncurses.so.3.0...(no debugging symbols found)...
 done.
 Reading symbols from /usr/lib/libgdbm.so.1...(no debugging symbols found)...
 done.
 Reading symbols from /usr/lib/libdb.so.1...(no debugging symbols found)...done.
 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done.
 Reading symbols from /lib/libc.so.5...(no debugging symbols found)...done.
 Reading symbols from /lib/ld-linux.so.1...(no debugging symbols found)...done.
 #0  0x40296bb5 in __kill ()
 (gdb) where
 #0  0x40296bb5 in __kill ()
 #1  0x806e70d in fatal_error_signal ()
 #2  0xbfffe56c in ?? ()
 #3  0xa29 in ?? ()
 Cannot access memory at address 0x616d2d6b.
 (gdb) quit


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .