From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation Date: Thu, 11 May 2023 13:06:15 +0300 Message-ID: <83jzxf5giw.fsf@gnu.org> References: <86wn1jtezk.fsf@gnu.org> <83jzxjcac9.fsf@gnu.org> <86h6smopo6.fsf@gnu.org> <835y92dfgd.fsf@gnu.org> <86v8h2k475.fsf@gnu.org> <83r0rqaycc.fsf@gnu.org> <86wn1h3dpz.fsf@gnu.org> <835y91brfv.fsf@gnu.org> <86fs849xb0.fsf@gnu.org> <83ild08i8j.fsf@gnu.org> <86y1lwmfcw.fsf@gnu.org> <83ild06sb5.fsf@gnu.org> <83a5yc6m2e.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38994"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63365@debbugs.gnu.org, akrl@sdf.org To: arash@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 11 12:06:27 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 1px3Bq-0009yq-CG for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 11 May 2023 12:06:26 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1px3BV-00046a-60; Thu, 11 May 2023 06:06:05 -0400 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 1px3BT-00040A-1u for bug-gnu-emacs@gnu.org; Thu, 11 May 2023 06:06:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1px3BS-00012Z-QM for bug-gnu-emacs@gnu.org; Thu, 11 May 2023 06:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1px3BS-0005in-EA for bug-gnu-emacs@gnu.org; Thu, 11 May 2023 06:06:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 11 May 2023 10:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63365 X-GNU-PR-Package: emacs Original-Received: via spool by 63365-submit@debbugs.gnu.org id=B63365.168379955521981 (code B ref 63365); Thu, 11 May 2023 10:06:02 +0000 Original-Received: (at 63365) by debbugs.gnu.org; 11 May 2023 10:05:55 +0000 Original-Received: from localhost ([127.0.0.1]:49766 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1px3BL-0005iT-DH for submit@debbugs.gnu.org; Thu, 11 May 2023 06:05:55 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:54906) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1px3BJ-0005iG-Fu for 63365@debbugs.gnu.org; Thu, 11 May 2023 06:05:54 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1px3BD-00010r-OF; Thu, 11 May 2023 06:05:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=cFVVaWWIuxpH8exHveKW1jmyWoqgi33cUPh1HIt78lI=; b=hBOWWvl0x7utTHNybZ5M 4jtKd/Rc5K9HIwLXDhT3UyWL+IiljXZ9t4MqcNTkoC1TUJ5gXi1lx8lF23dkWXgrttw1WBx9BcxZ3 Lhi4lrMYWc25+/5ORKuAHcwwSGAJTJQDJJxCdkb4ngMDwbT4KAPGHbZaaZKLrDFOP/j+ZqV8NqwVL iisWySBGIn/9EIcFQZBAgNUCc0U+qmPwyK3/EpN30ucuAm5roPOUdTVGPnQcio4AehGcVg0gkVVym 16u1a+ulm54Dc4549LUo5k22Tn2hKXUmiR3ZnoA9191Cavn/umL6DsznixjznjbDlWx4ZnzZ+8Khk Ii47Rqk2R3+bsQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1px3AZ-0005N0-MN; Thu, 11 May 2023 06:05:15 -0400 In-Reply-To: <83a5yc6m2e.fsf@gnu.org> (message from Eli Zaretskii on Wed, 10 May 2023 22:08:57 +0300) 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:261557 Archived-At: > Cc: 63365@debbugs.gnu.org, akrl@sdf.org > Date: Wed, 10 May 2023 22:08:57 +0300 > From: Eli Zaretskii > > > Cc: 63365@debbugs.gnu.org, akrl@sdf.org > > Date: Wed, 10 May 2023 19:54:06 +0300 > > From: Eli Zaretskii > > > > Maybe it's a bug in your addr2line, then. It works perfectly here, > > FWIW. > > > > Can you make the unstripped emacs.exe available for download > > somewhere, along with the emacs_backtrace.txt produced by that same > > binary? I'd like to take a look. > > Hmm... looking at the files you sent, I'm beginning to think something > is wrong with generating backtraces on MS-Windows in the 64-bit > builds. Maybe it has to do with ASLR, or maybe the code which > produces the backtrace is wrong in 64-bit executables. Actually, I take this back: the addresses in emacs_backtrace.txt seem reasonable, similar to addresses shown in GDB backtraces from a 64-bit Windows build we have on the bug tracker. So the suspicion goes back to addr2line, although I see the same problem with my version, which I built myself and which works flawlessly with the 32-bit MinGW build of Emacs. > I'd like to see the backtrace from GDB and compare the addresses there > with those in emacs_backtrace.txt. Did you try to run the crashing > command under GDB, as I described earlier? And also, please try the other method described in the manual: The hexadecimal numbers are program addresses, which can be associated with source code lines using a debugging tool. For example, the GDB command ‘list *0x509af6’ prints the source-code lines corresponding to the ‘emacs[0x509af6]’ entry. So could you try this method with a couple of addresses shown in emacs_backtrace.txt you have? Does "list *0xNNNNN" yield reasonable source locations?