From xemacs-m  Wed Sep 24 09:24:40 1997
Received: from gol1.gol.com (gol1.gol.com [202.243.48.4])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id JAA28115
	for <xemacs-beta@xemacs.org>; Wed, 24 Sep 1997 09:24:38 -0500 (CDT)
Received: from pentagana.camelot.jp (tc-6-101.tokyo.gol.ne.jp [203.216.10.101])
	by gol1.gol.com (8.8.7/8.8.7) with ESMTP id XAA20227
	for <xemacs-beta@xemacs.org>; Wed, 24 Sep 1997 23:24:37 +0900 (JST)
Received: (from jhod@localhost)
	by pentagana.camelot.jp (8.8.6/8.8.6) id XAA03129;
	Wed, 24 Sep 1997 23:19:35 +0900
To: xemacs-beta@xemacs.org
Subject: Re: Sarajevo spit out core
References: <hhafh3iivo.fsf@arioch.oche.de>
From: jareth@camelot-soft.com (P. E. Jareth Hein)
In-Reply-To: Carsten Leonhardt's message of "24 Sep 1997 03:46:19 +0200"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: 24 Sep 1997 23:19:35 +0900
Message-ID: <ohhgbau748.fsf@pentagana.camelot.jp>
Lines: 72
X-Mailer: Gnus v5.5/XEmacs 20.3(beta20) - "Tirana"

Carsten Leonhardt <leo@arioch.oche.de> writes:

> [1  <text/plain; US-ASCII (7bit)>]
> I was fumbling around in Quassia's group buffer, when I was left with
> the boring background of my window manager :-(
> 
> Quite a backtrace I got there. I'll keep the core around for a while.
> 
> Output on stderr was (exactly like this, without the usual message,
> and that line twice):
> 
> [2  <text/plain; US-ASCII (7bit)>]
> Fatal error: assertion failed, file eval.c, line 1908, abort()
> Fatal error: assertion failed, file eval.c, line 1908, abort()
> 
> [3  <text/plain; US-ASCII (7bit)>]
> $ gdb xemacs core
<snip>
> Reading symbols from /lib/ld-linux.so.1...done.
> #0  0x40256149 in __kill ()
> (gdb) bt
> #0  0x40256149 in __kill ()
> #1  0x4022540d in raise (sig=135851319)
> #2  0x808073e in signal_1 (sig={s = {type_mark = 5, val = -131370884}, 
>       gu = {type = Lisp_Type_Symbol, markbit = 0, val = 137064572}, 
>       i = -2101934139, v = 0x82b707c5, cv = 0x82b707c5}, data={s = {
>         type_mark = 2, val = -125577812}, gu = {type = Lisp_Type_Cons, 
>         markbit = 0, val = 142857644}, i = -2009244990, 
>       v = 0x883d5ac2, cv = 0x883d5ac2}) at eval.c:1908
<snip>
> #13 0x807daa4 in shut_down_emacs (sig=6, stuff={s = {type_mark = 5, 
>         val = -131371004}, gu = {type = Lisp_Type_Symbol, markbit = 0, 
>         val = 137064452}, i = -2101936059, v = 0x82b70045, 
>       cv = 0x82b70045}) at emacs.c:1914
> #14 0x807c44c in fatal_error_signal (sig=6) at emacs.c:195
> #15 0xbfff5b04 in ?? ()
> #16 0x4022540d in raise (sig=135851319)
> #17 0x808073e in signal_1 (sig={s = {type_mark = 5, val = -131370884}, 
>       gu = {type = Lisp_Type_Symbol, markbit = 0, val = 137064572}, 
>       i = -2101934139, v = 0x82b707c5, cv = 0x82b707c5}, data={s = {
>         type_mark = 2, val = -125577604}, gu = {type = Lisp_Type_Cons, 
>         markbit = 0, val = 142857852}, i = -2009241662, 
>       v = 0x883d67c2, cv = 0x883d67c2}) at eval.c:1908
> #18 0x8080d4c in signal_error (sig={s = {type_mark = 5, 
>         val = -131370884}, gu = {type = Lisp_Type_Symbol, markbit = 0, 
>         val = 137064572}, i = -2101934139, v = 0x82b707c5, 
>       cv = 0x82b707c5}, data={s = {type_mark = 2, val = -125577604}, 
>       gu = {type = Lisp_Type_Cons, markbit = 0, val = 142857852}, 
>       i = -2009241662, v = 0x883d67c2, cv = 0x883d67c2}) at eval.c:2075
<snip>
> #31 0x80f1b0f in Lstream_flush_out (lstr=0x8c76600) at lstream.c:386
> #32 0x80f2122 in Lstream_close (lstr=0x8c76600) at lstream.c:705
> #33 0x80f1796 in finalize_lstream (header=0x8c76600, for_disksave=0)
>     at lstream.c:189
> #34 0x805414b in sweep_lcrecords_1 (prev=0x827bf0c, used=0xbfff5efc)
>     at alloc.c:3184
> #35 0x8055043 in gc_sweep () at alloc.c:3823
> #36 0x80556fd in garbage_collect_1 () at alloc.c:4134

Let me guess: you're running on a machine that uses PPP or SLIP access 
to the net, and this core happened after you'd dropped the link.  Do I 
win a prize?

Anyways, there is a bug that happens when GCing a stream and the
stream wants to display an error.  I've had it bite me a couple of
times too, and will very probably get annoyed enough to fix it here
soon.  (after I finish my colormap stuff, and TIFF stuff, and....)

-- 
Jareth Hein
Camelot Software, Ltd.
jareth@camelot-soft.com

