From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.bugs Subject: bug#38912: 27.0.60; PDumper meets segmentation fault when evil is loaded Date: Mon, 6 Jan 2020 15:51:57 +0000 Message-ID: References: <333553AC-68DE-4F1C-9586-5A13248AD6DD@icloud.com> <83ftgvh96l.fsf@gnu.org> <83a771g2tc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="51423"; mail-complaints-to="usenet@blaine.gmane.org" Cc: NiwTinray , 38912@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jan 06 16:53:13 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ioUgq-000DGx-Qn for geb-bug-gnu-emacs@m.gmane.org; Mon, 06 Jan 2020 16:53:12 +0100 Original-Received: from localhost ([::1]:54064 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ioUgp-0008C6-CY for geb-bug-gnu-emacs@m.gmane.org; Mon, 06 Jan 2020 10:53:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50483) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ioUgh-00087X-1v for bug-gnu-emacs@gnu.org; Mon, 06 Jan 2020 10:53:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ioUgf-0005ND-WF for bug-gnu-emacs@gnu.org; Mon, 06 Jan 2020 10:53:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40566) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ioUgf-0005My-TC for bug-gnu-emacs@gnu.org; Mon, 06 Jan 2020 10:53:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ioUgf-0006UQ-Sd for bug-gnu-emacs@gnu.org; Mon, 06 Jan 2020 10:53:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Jan 2020 15:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38912 X-GNU-PR-Package: emacs Original-Received: via spool by 38912-submit@debbugs.gnu.org id=B38912.157832596024918 (code B ref 38912); Mon, 06 Jan 2020 15:53:01 +0000 Original-Received: (at 38912) by debbugs.gnu.org; 6 Jan 2020 15:52:40 +0000 Original-Received: from localhost ([127.0.0.1]:46539 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ioUgK-0006Tp-6c for submit@debbugs.gnu.org; Mon, 06 Jan 2020 10:52:40 -0500 Original-Received: from mail-ot1-f43.google.com ([209.85.210.43]:44075) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ioUgI-0006TY-Uz for 38912@debbugs.gnu.org; Mon, 06 Jan 2020 10:52:39 -0500 Original-Received: by mail-ot1-f43.google.com with SMTP id h9so69623518otj.11 for <38912@debbugs.gnu.org>; Mon, 06 Jan 2020 07:52:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kak+O91xVS7l6S7dzJdrAMxWCydNRkC2IFYSS8RTL7w=; b=bYY89wpsvYy03RaBC/B86OROzXqRei/oYzZzweBATQ/Cp/QkTg2u+qBb58fmdXZXgu kFfdGdA+lAOpm7VVEUmqmNq8PRT+tqw9KHk/+h//Ts5CTcNWYIGZ6Cv9V94egktmjkDU k1eDhoUMOxrQXI8kTo35GJ6HD4xoDZqeO1quPkcOQK1EPBiBP6nA0O83pQFcnQYCalSq c/G8U+z+opakGZGX6n1Dp99xhbcB9IVWT0i/E2zjvyV7gQaXUKfObd5Q6ctn0uBAGe/R XhPorSkZH8aN7TaV38rt62UL0Wbnq1d4iiob79/Z+WKwnwpFHzG6HSepvCawJuNRxds6 1S4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kak+O91xVS7l6S7dzJdrAMxWCydNRkC2IFYSS8RTL7w=; b=emUTSNs4yHB+2qCdAeGPdTOZ8XD8Tjhd46uP+e6DinkgR0OQH8liuIRGsTTg/o1Ui7 Qgpscj89MjZxXGueqUQcADmJ9jWVqdFimzfsA0oWevDbBSoc+YhrH7O3ZI7C67rR2+II iH+o43woumK1MUszhruesnP85BPzWTx08fmHOAgS/VP5XtcNHRahT0IiE/bHch2RS6MI 8WEzmRFt6niICL5ObZ8nbNw7qCKmOSs15uY9WHhJi+rCWaFStJecZZqCKFcmJ2OoGFt3 GD2Cej5UwD+cRTlm//Qk5z01I9C9lIbwTEbF7OJZETcpYds2F0LoCe3Uilf5X85TYPjG b+Qg== X-Gm-Message-State: APjAAAX0Cduj2cvxHDFyRotlsXgmKv0J7WqipigZCWmQHV/vN65bQ8V0 +vSHet1taViu9B57E4Ps4TQT1pEKbmC/NlL1eJ4= X-Google-Smtp-Source: APXvYqyxFv7rMZrLmWP8h/PEMaPKHzlcIjl4AyGU+PjQkNAmwiupfDV4mErsqjOua8b6lCF4p+R0lQHXDwJcEFAfh5U= X-Received: by 2002:a05:6830:1bd5:: with SMTP id v21mr123019042ota.154.1578325953230; Mon, 06 Jan 2020 07:52:33 -0800 (PST) In-Reply-To: <83a771g2tc.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:174238 Archived-At: On Sun, Jan 5, 2020 at 6:46 PM Eli Zaretskii wrote: > In my debug build of Emacs 27.0.60 I get an assertion violation while > dumping, which probably is already a sign of trouble. I think that's unrelated, but here's some analysis anyway, in case we want to fix this bug: Different bytecode objects may be `equal', but have different sxhashes. (equal #[0 "" [] 0] #[0 "" [] 0]) (sxhash #[0 "" [] 0]) (sxhash #[0 "" [] 0]) When such bytecodes are used as keys for a hash table using hashfn_equal, I believe the result is, fairly obviously, two hash table entries for equal keys; when the hash table is rehashed, we may be unlucky enough to retrieve the wrong one, leading to the crash. That's what cl-generic.el does for the table cl--generic-dispatchers, which I believe is what you were looking at. > #2 0x01326817 in check_hash_table_rehash (table_orig=XIL(0xa000000006288090)) > at pdumper.c:2684 Can you confirm table_orig is cl--generic-dispatchers? 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.