GNU bug report logs - #47244
28.0.50; SIGSEGV in long-runnning Emacs

Previous Next

Package: emacs;

Reported by: Michael Welsh Duggan <md5i <at> md5i.com>

Date: Thu, 18 Mar 2021 15:40:01 UTC

Severity: normal

Found in version 28.0.50

Done: Michael Welsh Duggan <mwd <at> md5i.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Welsh Duggan <mwd <at> md5i.com>
Cc: mwd <at> md5i.com, rudalics <at> gmx.at, 47244 <at> debbugs.gnu.org, schwab <at> linux-m68k.org, mwd <at> cert.org
Subject: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Thu, 01 Apr 2021 16:22:29 +0300
> From: Michael Welsh Duggan <mwd <at> md5i.com>
> Cc: martin rudalics <rudalics <at> gmx.at>,  mwd <at> cert.org,  mwd <at> md5i.com,
>   schwab <at> linux-m68k.org,  47244 <at> debbugs.gnu.org
> Date: Thu, 01 Apr 2021 09:20:48 -0400
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> Cc: Eli Zaretskii <eliz <at> gnu.org>, "mwd <at> md5i.com" <mwd <at> md5i.com>,
> >>  "schwab <at> linux-m68k.org" <schwab <at> linux-m68k.org>,
> >>  "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>
> >> From: martin rudalics <rudalics <at> gmx.at>
> >> Date: Thu, 1 Apr 2021 09:14:06 +0200
> >> 
> >> Otherwise I'm clueless.  Maybe Eli has an idea.
> >
> > I would like first to understand what prevents Emacs from starting.
> > Does it crash at that point, i.e. inside the call to
> > BUFFER_CHECK_INDIRECTION? if so, can Michael please try to identify
> > what is the immediate cause of the crash?
> 
> And I find I can't ansswer the question.  I rebuilt to give that
> information, and this time everything is working just fine with
> --enable-checking and the most recent debugging patch.  No idea what
> happened yesterday.

Great, thanks.

> I will say that what happened yesterday was not a crash.  It was a
> breakpoint on the
> 
>     error ("Selecting deleted buffer");
> 
> libe that was added to set_buffer_internal_2.  I think maybe I overused
> that gdb session and it got confused.  I'm running now with the latest
> patch and we'll see if the problem triggers today.

There's no need to debug problems that cannot be reproduced.




This bug report was last modified 4 years and 28 days ago.

Previous Next


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