unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregor Zattler <telegraph@gmx.net>
Cc: 56862@debbugs.gnu.org
Subject: bug#56862: 29.0.50; crashes while compiling native code
Date: Sun, 31 Jul 2022 22:09:48 +0300	[thread overview]
Message-ID: <838ro93xqb.fsf@gnu.org> (raw)
In-Reply-To: <877d3txg5y.fsf@no.workgroup> (message from Gregor Zattler on Sun, 31 Jul 2022 20:58:49 +0200)

> From: Gregor Zattler <telegraph@gmx.net>
> Date: Sun, 31 Jul 2022 20:58:49 +0200
> 
> Dear emacs developers, earlier today a did build with the
> then most recent Emacs sources
> (107f832577123ea7ebe867cba55601d0142f546f) on a up-to-date
> Debian bullseye.  This was *not* a fresh checkout / make bootstrap.
> 
> GNU Emacs 29.0.50 (build 6, x86_64-pc-linux-gnu, X toolkit, cairo version 1.16.0) of 2022-07-31
> 
> This Emacs build was configured like so:
> 
> ./autogen.sh && ./configure -C $PREFIX
> --enable-locallisppath=/etc/emacs:/usr/local/share/emacs/${EMACSMAJORVERSION}.${EMACSMINORVERSION}/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/${EMACSMAJORVERSION}.${EMACSMINORVERSION}/site-lisp:/usr/share/emacs/site-lisp
> --with-sound=yes --without-gconf --with-mailutils --build
> x86_64-linux-gnu
> --infodir=/usr/local/share/info:/usr/share/info --with-json
> --with-file-notification=yes --with-cairo --with-x=yes
> --with-x-toolkit=lucid --without-toolkit-scroll-bars
> --enable-checking=yes,glyphs --enable-check-lisp-object-type
> --with-native-compilation
> 
> 
> CFLAGS=-g3 -O0 -ffile-prefix-map=/home/grfz/src/emacs-master=. -fstack-protector-strong -Wformat -Werror=format-security
> 
> 
> After starting up Emacs with my configuration it started
> compiling native code and after a few minutes it crashed.  I
> realized that this also happens with
> 
> emacs -Q -nw init.el

From the only readable backtrace, the one you produced from GDB, I can
only deduce that some timer was run by Emacs, and that timer's code
caused the crash in some way.  It's hard to say more, especially since
your GDB seems to be misconfigured and causes Python exceptions
instead of showing useful information.

If you can reproduce this at will, please try producing a GDB
backtrace after you fix your GDB installation.  And please try a newer
checkout of the master branch.

Thanks.





  reply	other threads:[~2022-07-31 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 18:58 bug#56862: 29.0.50; crashes while compiling native code Gregor Zattler
2022-07-31 19:09 ` Eli Zaretskii [this message]
2022-08-01  8:55   ` Gregor Zattler
2022-08-01 16:44     ` Eli Zaretskii
2022-08-02 12:01       ` Gregor Zattler
2022-08-21 15:25         ` Lars Ingebrigtsen

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=838ro93xqb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56862@debbugs.gnu.org \
    --cc=telegraph@gmx.net \
    /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).