GNU bug report logs - #56862
29.0.50; crashes while compiling native code

Previous Next

Full log

Message #8 received at 56862 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gregor Zattler <telegraph <at> gmx.net>
Cc: 56862 <at> debbugs.gnu.org
Subject: Re: bug#56862: 29.0.50; crashes while compiling native code
Date: Sun, 31 Jul 2022 22:09:48 +0300

> From: Gregor Zattler <telegraph <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.