Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Cc: xemacs-beta@xemacs.org, ding@gnus.org
Subject: Re: crash
Date: 02 Mar 2000 18:01:47 +0100	[thread overview]
Message-ID: <byg0u971c4.fsf@math.ethz.ch> (raw)
In-Reply-To: Michael Harnois's message of "02 Mar 2000 09:38:07 -0600"

Michael Harnois <mdharnois@home.com> writes:

You did say you could reproduce this?

>     > If it is a crash, then it is xemacs and you need to give more
>     > info. C backtrace and version to be precise ('latest cvs' is
>     > very ambiguous)
> #2  0x805608b in xrealloc (block=0x87148b8, size=9600)
>     at /usr/src/xemacs-21.2/src/alloc.c:296

This seems ok.. 

> #3  0x808cd18 in record_unwind_protect (
>     function=0x81145fc <change_function_restore>, arg={gu = {
>         type = Lisp_Type_Record, val = 36618428}, s = {bits = 0, 
>         val = 73236856}, u = {bits = 0, val = 73236856}, ui = 146473712, 
>       i = 146473712, v = 0x8bb02f0, cv = 0x8bb02f0})
>     at /usr/src/xemacs-21.2/src/eval.c:4455
> #4  0x8111039 in signal_before_change (buf=0x8bb02f0, start=1, end=1)
>     at /usr/src/xemacs-21.2/src/insdel.c:2174

Maybe Hrvoje has an idea. Although this is before the extent
modification stuff.

The only thing is that your bracktrace looks very deep. Maybe we are
running out of stackspace somewhere?

Jan




  reply	other threads:[~2000-03-02 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-01  3:59 crash Michael Harnois
2000-03-01  8:13 ` crash Jan Vroonhof
2000-03-01 14:54   ` Identifying CVS version (was: Re: crash) lconrad
2000-03-01 23:00     ` Neil Crellin
2000-03-03 17:33     ` Jan Vroonhof
2000-03-02 15:38   ` crash Michael Harnois
2000-03-02 17:01     ` Jan Vroonhof [this message]
2000-03-02 20:06       ` crash Michael Harnois
2000-03-03  8:39         ` crash Jan Vroonhof
2000-03-03 15:13           ` crash Michael Harnois

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=byg0u971c4.fsf@math.ethz.ch \
    --to=vroonhof@math.ethz.ch \
    --cc=ding@gnus.org \
    --cc=xemacs-beta@xemacs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).