GNU bug report logs - #22120
25.1.50; segfault while running circe

Previous Next

Full log

Message #56 received at 22120 <at> debbugs.gnu.org (full text, mbox):

From: Eric Hanchrow <eric.hanchrow <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22120 <at> debbugs.gnu.org
Subject: Re: bug#22120: Another backtrace
Date: Sun, 13 Dec 2015 18:07:43 +0000

[Message part 1 (text/plain, inline)]

I'm surprised that it is possible to cause a segfault from lisp.  Is that
an indication of a problem in the core C code, or is that just the way
things are?

On Sun, Dec 13, 2015 at 10:04 AM Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Eric Hanchrow <eric.hanchrow <at> gmail.com>
> > Date: Sun, 13 Dec 2015 17:54:04 +0000
> > Cc: 22120 <at> debbugs.gnu.org
> >
> >     Looks like another reincarnation of bug#21667.
> >
> > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21667 appears to be
> unrelated to
> > this one. I suspect you made a typo.
>
> Sorry, I meant 21666.
>
> >     Can you modify lui-adjust-undo-list so that GC is inhibited (by
> >     binding gc-cons-threshold to most-positive-fixnum around the whole
> >     function)?
> >
> > OK, I've done that. If that works, it'll take days of use before I'm
> confident
> > that it did work (because the bug only appears once every few days); can
> you
> > think of some sort of debug message I can stick in there that can tell
> us that
> > you've correctly guessed the cause?
>
> No, I don't think it's possible, not during GC anyway.
>
> There's no hurry, so waiting for this to happen is fine.  Thanks.
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.