unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>, Andrea Corallo <akrl@sdf.org>
Cc: 63365@debbugs.gnu.org
Subject: bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation
Date: Mon, 08 May 2023 14:48:54 +0300	[thread overview]
Message-ID: <83jzxjcac9.fsf@gnu.org> (raw)
In-Reply-To: <86wn1jtezk.fsf@gnu.org> (message from Arash Esbati on Mon, 08 May 2023 10:16:31 +0200)

> From: Arash Esbati <arash@gnu.org>
> Date: Mon, 08 May 2023 10:16:31 +0200
> 
> --8<---------------cut here---------------start------------->8---
>   ELC+ELN  ../lisp/font-core.elc
>   ELC+ELN  ../lisp/font-lock.elc
>   ELC+ELN  ../lisp/format.elc
>   ELC+ELN  ../lisp/frame.elc
> 
> Error: wrong-type-argument ("../lisp/frame.el" number-or-marker-p
> Backtrace:
> 00007ff6e577a12e
> 00007ff6e5648be1
> 00007ff6e5669601
> 00007ff6e57de84a
> 00007ff9b7977ff0

These addresses are not useful anywhere but on your system.  So either
run this command under GDB and post a human-readable source-level
backtrace, or at least convert the above list of addresses to a list
of file names, function names, and line numbers as explained in the
node "Crashing" of the Emacs user manual.

Thanks.





  reply	other threads:[~2023-05-08 11:48 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  8:16 bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation Arash Esbati
2023-05-08 11:48 ` Eli Zaretskii [this message]
2023-05-08 14:36   ` Arash Esbati
2023-05-08 15:13     ` Eli Zaretskii
2023-05-08 19:34       ` Arash Esbati
2023-05-09  5:05         ` Eli Zaretskii
2023-05-09 12:12           ` Arash Esbati
2023-05-09 12:49             ` Eli Zaretskii
2023-05-10 12:37               ` Arash Esbati
2023-05-10 12:48                 ` Eli Zaretskii
2023-05-10 14:27                   ` Arash Esbati
2023-05-10 16:54                     ` Eli Zaretskii
2023-05-10 19:08                       ` Eli Zaretskii
2023-05-11 10:06                         ` Eli Zaretskii
2024-01-26 13:11                           ` Eli Zaretskii
2024-01-26 18:24                             ` Arash Esbati
2024-01-26 18:59                               ` Eli Zaretskii
2024-01-26 20:33                                 ` Arash Esbati
2024-02-01 10:39                                   ` Arash Esbati
2024-02-01 11:02                                     ` Eli Zaretskii
2024-02-01 11:11                                       ` Arash Esbati
2024-02-01 11:27                                         ` Eli Zaretskii
2023-05-26 13:05                         ` Arash Esbati
2023-05-26 13:42                           ` Eli Zaretskii
2023-05-26 19:21                             ` Arash Esbati
2023-05-27  6:00                               ` Eli Zaretskii
2023-05-27 10:57                                 ` Arash Esbati
2023-05-27 11:33                                   ` Eli Zaretskii
2023-05-27 17:35                                     ` Arash Esbati
2023-05-28  6:55                                       ` Eli Zaretskii
2023-06-01  7:31                                         ` András Svraka
2023-06-01  7:37                                           ` András Svraka
2023-06-01  8:42                                             ` Eli Zaretskii
2023-06-01  8:49                                               ` Andrea Corallo
2023-06-01 15:33                                                 ` András Svraka
2023-06-01 15:30                                               ` András Svraka
2023-06-01 16:25                                                 ` Eli Zaretskii
2023-06-08 10:21                                         ` Arash Esbati
2023-06-08 13:19                                           ` Eli Zaretskii
2023-06-08 14:02                                             ` Andrea Corallo
2023-06-08 14:18                                               ` Eli Zaretskii
2023-06-08 14:39                                                 ` Andrea Corallo
2023-06-08 22:08                                             ` Arash Esbati
2023-06-08 22:27                                         ` Arash Esbati
2023-06-16  9:04 ` Cyril Arnould
2023-06-16 10:31   ` Eli Zaretskii
2023-06-16 14:49     ` Andrea Corallo
2023-06-16 14:52       ` Andrea Corallo
2023-06-22 20:34   ` Arash Esbati
2023-06-23  5:32     ` Eli Zaretskii
2023-06-23 11:41       ` Arash Esbati
2023-06-23 12:15         ` Eli Zaretskii
2023-06-23 12:50           ` Arash Esbati
2023-06-24  9:17           ` Deus Max
2023-06-24  9:21             ` Eli Zaretskii
2023-06-24 14:41               ` Deus Max
2023-06-24 15:05                 ` Eli Zaretskii
2023-06-25 13:51       ` Andrea Corallo
2023-06-25 15:41         ` Eli Zaretskii
2023-06-25 18:11           ` Andrea Corallo
2023-06-25 18:31             ` Eli Zaretskii
2023-06-26  7:03               ` Andrea Corallo
2023-06-26 22:04 ` Cyril Arnould
2023-06-27  2:30   ` Eli Zaretskii
2023-06-27 19:28 ` Cyril Arnould
2023-06-27 20:22   ` Andrea Corallo
2023-06-28 11:37   ` Eli Zaretskii
2023-06-28 23:16 ` Cyril Arnould
2023-06-29  5:20   ` Eli Zaretskii
2023-06-29  6:36 ` Cyril Arnould
2023-06-29  8:21   ` Andrea Corallo
2023-06-29  9:16     ` bug#63365: AW: " Cyril Arnould
     [not found] <AS4PR10MB6110F1445D9658E48521DDD2E358A@AS4PR10MB6110.EURPRD10.PROD.OUTLOOK.COM>
2023-06-20  8:31 ` Andrea Corallo

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83jzxjcac9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63365@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=arash@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).