From: Vivek Dasmohapatra <vivek@etla.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 26932@debbugs.gnu.org
Subject: bug#26932: Found the triggering behaviour
Date: Mon, 20 Jan 2020 15:11:41 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.02.2001201509390.11208@platypus.pepperfish.net> (raw)
In-Reply-To: <87ftjjixua.fsf@gnus.org>
> If I understand correctly, the external lui package set buffer-undo-list
> to something invalid, and this led Emacs to segfault when gc-ing?
Not invalid as such - entries were removed from the list while it was "in
flight" through a mapc/mapcar and a double free (or similar) occurred.
> Was there any further work done here, or a reproducible test case
> written?
No test case was written, the code for lui was changed to operate on
a copy of the undo list, then assign that back to the original head
variable instead.
next prev parent reply other threads:[~2020-01-20 15:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 20:54 bug#26932: 25.1; Crash triggered a few times a day with network process Vivek Dasmohapatra
2017-05-15 3:04 ` Eli Zaretskii
2017-05-15 11:18 ` Vivek Dasmohapatra
2017-06-11 21:39 ` Vivek Dasmohapatra
2017-06-12 14:10 ` Eli Zaretskii
2017-06-12 15:21 ` Vivek Dasmohapatra
2017-06-12 15:51 ` Eli Zaretskii
2017-06-12 15:56 ` Vivek Dasmohapatra
2017-06-12 16:30 ` Eli Zaretskii
2017-06-13 15:41 ` Vivek Dasmohapatra
2017-06-13 16:41 ` Eli Zaretskii
2017-06-13 17:04 ` Vivek Dasmohapatra
2017-06-13 19:46 ` Eli Zaretskii
2017-06-13 21:23 ` Vivek Dasmohapatra
2017-06-14 2:32 ` Eli Zaretskii
2017-06-15 13:48 ` Vivek Dasmohapatra
2017-06-15 14:47 ` Eli Zaretskii
2017-06-19 0:57 ` Vivek Dasmohapatra
2017-06-19 14:59 ` Eli Zaretskii
2017-06-19 18:03 ` Vivek Dasmohapatra
2017-07-10 13:01 ` bug#26932: Subject: Re: bug#26932: 25.1; Vivek Dasmohapatra
2018-01-10 13:58 ` bug#26932: Found the triggering behaviour Vivek Dasmohapatra
2019-10-23 10:02 ` Lars Ingebrigtsen
2020-01-20 15:11 ` Vivek Dasmohapatra [this message]
2020-01-22 13:30 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.2001201509390.11208@platypus.pepperfish.net \
--to=vivek@etla.org \
--cc=26932@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).