[Bug: 21.5-b28]

Soren Feodor Nielsen feodor at stat.ku.dk
Tue Feb 12 08:04:48 EST 2008


Hi again

I've managed to reproduce the crash but not when starting from "xemacs 
-vanilla". I'll be happy to try to get you more information if you are 
interested (I think I've worked out how to avoid the crash; it only 
happens when I change fonts while having a large LaTeX-file in xemacs, so 
it is not really a problem for me).

I've tried the "gdb 'which xemacs' | tee -a ~/gdb.out" command but with 
little luck. I do get output (I attach gdb.out) but I haven't been able to 
start xemacs and therefore cannot reproduce the crash while gdb is 
running. It is probably me who's stupid; maybe you could tell me exactly 
what I should do? It may be useful to know that I am working on a 
suse-linux machine (10.something)

Best regards

Feodor

On Sun, 10 Feb 2008, Stephen J. Turnbull wrote:

> Søren Feodor Nielsen writes:
>
> > XEmacs crashed for me when I was trying to change the font; below is
> > the output.
>
> It would be very helpful if you can give us an exact sequence of
> keystrokes and/or mouse gestures to reach the crash starting from
> "xemacs -vanilla" on the command line.  Without that we may be unable
> to reproduce the crash.
>
> > I had little luck in obtaining the "C stack backtrace" following
> > the directions below.
>
> We really need to get a C backtrace to debug the problem.  A crash is
> *never* the fault of Lisp code; Lisp code cannot crash. ;-) However,
> the C implementation of Lisp primitives can.
>
> I believe that Red Hat-derived distros such as Fedora have a special
> place they put core files, and they are named something like
> "core.$$12345" or "xemacs.$$12345" where the "12345" is the process ID
> of the XEmacs that crashed.  If you can't find that core, but can
> reproduce the crash, you can do "gdb `which xemacs` | tee -a
> ~/gdb.out", then type "run" to gdb, reproduce the crash, and finally
> "bt".  The "tee" command allows you to capture the output in the file
> ~/gdb.out which you can just attach to your post.
>
>
>


    ASCII RIBBON    /"\  Statistics Division
  CAMPAIGN AGAINST  \ /  Universitetsparken 5  Ph:  (+45) 35 32 07 95
     HTML MAIL       X   DK-2100 Kbh O         Fax: (+45) 35 32 07 72
                    / \  DENMARK
-------------- next part --------------
[?1034hGNU gdb 6.6.50.20070726-cvs
Copyright (C) 2007 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-suse-linux"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/xemacs 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

[Thread debugging using libthread_db enabled]
[New Thread 0xb79348d0 (LWP 5567)]

Program exited with code 0377.
(gdb) quit


More information about the XEmacs-Beta mailing list