From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Chang Xiaoduan Newsgroups: gmane.emacs.bugs Subject: bug#67900: 30.0.50; Emacs Crahes When Executing Command `consult-buffer' Date: Thu, 21 Dec 2023 11:26:05 +0800 Message-ID: References: <838r5qib7l.fsf@gnu.org> <83plz1ggua.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34272"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 67900@debbugs.gnu.org, Andrea Corallo To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Dec 21 05:52:15 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rGB2d-0008k8-Ke for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 21 Dec 2023 05:52:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rGB2Q-0004ax-22; Wed, 20 Dec 2023 23:52:02 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rGB2N-0004ai-59 for bug-gnu-emacs@gnu.org; Wed, 20 Dec 2023 23:51:59 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rGB2M-0001Ji-T1 for bug-gnu-emacs@gnu.org; Wed, 20 Dec 2023 23:51:58 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rGB2Q-0007o8-Gm for bug-gnu-emacs@gnu.org; Wed, 20 Dec 2023 23:52:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Chang Xiaoduan Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 21 Dec 2023 04:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 67900 X-GNU-PR-Package: emacs Original-Received: via spool by 67900-submit@debbugs.gnu.org id=B67900.170313431129974 (code B ref 67900); Thu, 21 Dec 2023 04:52:02 +0000 Original-Received: (at 67900) by debbugs.gnu.org; 21 Dec 2023 04:51:51 +0000 Original-Received: from localhost ([127.0.0.1]:42210 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rGB2C-0007nK-Hk for submit@debbugs.gnu.org; Wed, 20 Dec 2023 23:51:51 -0500 Original-Received: from r3-17.sinamail.sina.com.cn ([202.108.3.17]:42087) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rG9he-0006JN-VL for 67900@debbugs.gnu.org; Wed, 20 Dec 2023 22:26:35 -0500 X-SMAIL-HELO: PWRD-20210716KV Original-Received: from unknown (HELO PWRD-20210716KV)([111.207.225.84]) by sina.com (10.182.253.22) with ESMTP id 6583B04D00001BBF; Thu, 21 Dec 2023 11:26:20 +0800 (CST) X-Sender: drcxd@sina.com X-Auth-ID: drcxd@sina.com Authentication-Results: sina.com; spf=none smtp.mailfrom=drcxd@sina.com; dkim=none header.i=none; dmarc=none action=none header.from=drcxd@sina.com X-SMAIL-MID: 6009166816196 X-SMAIL-UIID: EB8AF9C6F2D845E2A7B3E381FACC6852-20231221-112620-1 In-Reply-To: <83plz1ggua.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 Dec 2023 15:10:21 +0200") X-Mailman-Approved-At: Wed, 20 Dec 2023 23:51:45 -0500 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:276608 Archived-At: Eli Zaretskii writes: > [Please use Reply All to reply, to keep the bug tracker CC'ed.] > This is the first time I report an Emacs bug using E-mails and I am not familiar with this kind of workflow for reporting a bug and communication. I have raised some issues on GitHub but that is totally different and more intuitive. Would you mind introducing me how such a workflow came into being and why you stick with it? Any links to wiki or articles are welcomed. > > The above seems to indicate the problems are somehow related to native > compilation. Can you build Emacs without native-compilation, and try > reproducing this in such an Emacs? If the problem doesn't happen in > Emacs without native-compilation, I suspect this is a MinGW GCC bug, > not an Emacs bug: the native code in *.eln files is somehow invalid. I can not reproduce the crash using Emacs without native-compilation. > > Which version of GCC do you have installed, and is libgccjit you have > is from the same GCC version? I am using gcc 13.2.0 and mingw-w64-x86_64-libgccjit 13.2.0-3. > > Or maybe we have a bug in native compilation. Andrea, can you try > reproducing this on GNU/Linux? > > Another idea is to modify comp.el to have native-comp-speed default to > 1 instead of 2, then rebuild Emacs ("make bootstrap") with CFLAGS='-O1', > and see if the problem goes away. If it does, that again points > toward GCC/libgccjit and the compiler optimizations. I have modified the `native-comp-speed` to 1, but not specified `CFLAGS='-O1'`. Though, the resulting Emacs binary does not reproduce the same crash. After all, it looks like Eli's assumption is likely to be true. If you are familiar with reporting a compiler bug, could you tell me how could I verify it is indeed a MinGW GCC bug and report this to MinGW?