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: Michael Welsh Duggan <mwd <at> cert.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: "mwd <at> md5i.com" <mwd <at> md5i.com>, "47244 <at> debbugs.gnu.org" <47244 <at> debbugs.gnu.org>, Eli Zaretskii <eliz <at> gnu.org>, "schwab <at> linux-m68k.org" <schwab <at> linux-m68k.org>
Subject: bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
Date: Wed, 31 Mar 2021 15:18:42 -0400
Michael Welsh Duggan <mwd <at> cert.org> writes:

> martin rudalics <rudalics <at> gmx.at> writes:
>
>>  > I have no idea what changed to cause this, but with this current
>>  > patchset I can't actually start emacs.
>>  >
>>  > #0 set_buffer_internal_2 (b=0x7ffff2a3cb10) at
>>  > ../../master/src/buffer.c:2157
>>  >          old_buf = 0x0
>>  >          tail = XIL(0x7ffff2a3cb15)
>>
>> I doubt that my last additions can have cause that and line 2157 is
>>
>>    BUFFER_CHECK_INDIRECTION (b);
>>
>> so I wonder what could have gone wrong here.  Maybe some pdumper snafu?
>>
>> Does it start with emacs -Q? 
>
> Nope.  It fails.
>
>> Does it start with --enable-checking=no?
>
> Yes.
>
>> Does it start without the changeset applied?
>
> Yes.

Also verified that using with the previous changeset with
--enable-checking=yes still works.

-- 
Michael Welsh Duggan
(mwd <at> cert.org)




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.