From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 8ba156f: Attempt to avoid crashes in plist-member
Date: Tue, 13 Oct 2015 17:58:42 +0300 [thread overview]
Message-ID: <83io6azufx.fsf@gnu.org> (raw)
In-Reply-To: <561C7C26.3060408@cs.ucla.edu>
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 12 Oct 2015 20:36:06 -0700
>
> QUIT could call some Lisp.
>
> Sure, but Lisp cannot affect the value of CONSP (plist).
Not the value of CONSP, the list itself. We follow the CONSP test
with XCAR, which crashed. The only way I could imagine that happening
is that the list got modified between the test and the XCAR call. Is
there any other way to explain that?
> How else would you explain a segfault in that loop?
>
> It's not clear the code is in that loop.
The address clearly points to Fplist_member at fns.c:2879.
> It could merely be RtlCaptureStackBackTrace misbehaving, no?
I don't think so. It could be something else, though: the segfault
could have happened in another thread while the Lisp thread was in
plist-member.
But the change I made cannot do any harm, and it tried to use the only
evidence I had from the report. The alternative was to do nothing at
all.
next prev parent reply other threads:[~2015-10-13 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151012170324.17966.77@vcs.savannah.gnu.org>
[not found] ` <E1ZlgVQ-0004gO-Em@vcs.savannah.gnu.org>
2015-10-13 1:07 ` [Emacs-diffs] master 8ba156f: Attempt to avoid crashes in plist-member Stefan Monnier
2015-10-13 2:42 ` Eli Zaretskii
2015-10-13 3:36 ` Paul Eggert
2015-10-13 14:58 ` Eli Zaretskii [this message]
2015-10-13 15:08 ` David Kastrup
2015-10-13 15:32 ` Eli Zaretskii
2015-10-13 15:50 ` David Kastrup
2015-10-13 15:21 ` Paul Eggert
2015-10-13 15:34 ` Eli Zaretskii
2015-10-13 19:05 ` Stefan Monnier
2015-10-13 8:00 ` Andreas Schwab
2015-10-13 15:01 ` Eli Zaretskii
2015-10-13 10:26 ` David Kastrup
2015-10-13 13:23 ` Stefan Monnier
2015-10-13 13:41 ` David Kastrup
2015-10-13 15:16 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83io6azufx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.