bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs


From: Michael Welsh Duggan
Subject: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Tue, 23 Mar 2021 11:08:36 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Michael Welsh Duggan <mwd@cert.org>
>> Cc: "mwd@md5i.com" <mwd@md5i.com>,
>>         "schwab@linux-m68k.org"
>>  <schwab@linux-m68k.org>,
>>         "47244@debbugs.gnu.org" <47244@debbugs.gnu.org>
>> Date: Tue, 23 Mar 2021 10:18:25 -0400
>> 
>> >   break buffer.c:1840 if redisplaying_p != 0 && b->window_count > 0
>> 
>> This triggered today.
>> 
>> #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


-- 
Michael Welsh Duggan
(mwd@cert.org)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]