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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Welsh Duggan <mwd <at> cert.org>
Cc: mwd <at> md5i.com, 47244 <at> debbugs.gnu.org, schwab <at> linux-m68k.org
Subject: Re: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Tue, 23 Mar 2021 18:42:25 +0200

> From: Michael Welsh Duggan <mwd <at> cert.org>
> Cc: "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>
> Date: Tue, 23 Mar 2021 11:08:36 -0400
> 
> >> #0  0x00005555555e1b6d in redisplay_internal ()
> >>     at ../../master/src/xdisp.c:15789
> >
> > I don't understand: the breakpoint was supposed to be on line 1840 in
> > buffer.c, so why does frame #0 show line 15789 in xdisp.c?  What am I
> > missing here?  Is this the right backtrace?
> 
> My mistake.  It was a segfault.  The breakpoint did not trigger.  Here's
> the breakpoint in question:
> 
> 5       breakpoint     keep y   0x0000555555713580 in Fkill_buffer 
>                                                    at ../../master/src/buffer.c:1840 inf 1, 2
>         stop only if redisplaying_p != 0 && b->window_count > 0

Then I guess the hypothesis about the scenario which causes the crash
was wrong.  Let's see if Martin's suggestion has better luck.

Previous Next

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