GNU bug report logs - #38912
27.0.60; PDumper meets segmentation fault when evil is loaded

Previous Next

Package: emacs;

Reported by: NiwTinray <niwtrx <at> icloud.com>

Date: Sat, 4 Jan 2020 03:27:02 UTC

Severity: normal

Merged with 32503

Found in versions 26.1, 27.0.60

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Daniel Colascione" <dancol <at> dancol.org>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: niwtrx <at> icloud.com, 38912 <at> debbugs.gnu.org, pipcet <at> gmail.com
Subject: Re: bug#38912: 27.0.60; PDumper meets segmentation fault when evil
 is loaded
Date: Mon, 06 Jan 2020 19:25:30 +0200
> Date: Mon, 6 Jan 2020 09:01:24 -0800
> From: "Daniel Colascione" <dancol <at> dancol.org>
> Cc: "Pip Cet" <pipcet <at> gmail.com>,
>  niwtrx <at> icloud.com,
>  dancol <at> dancol.org,
>  38912 <at> debbugs.gnu.org
> 
> >> Again, I doubt this is related to the original bug. That `equal'
> >> behaves weirdly like this is a problem I've mentioned before (when
> >> (equal a b) signals but (equal b a) succeeds), but the consensus then
> >> was not to change it, so it's possible this is only the rehashing
> >> check needing to be more careful.
> 
> This consensus is wrong. We need to make equality imply sxhash equality or
> very odd things (like this) will happen. C++ and Java both require this
> relationship between hash code equality and object equality, and we should
> too. Can we just fix the bytecode sxhash bug?

That'd be fine with me, especially since the ELisp manual seems to say
this is indeed a bug.




This bug report was last modified 3 years and 21 days ago.

Previous Next


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