From: Eli Zaretskii <eliz@gnu.org>
To: Henrik Grimler <henrik@grimler.se>
Cc: 39577@debbugs.gnu.org
Subject: bug#39577: 27.0.60; Assertion failed during compilation
Date: Thu, 13 Feb 2020 16:57:26 +0200 [thread overview]
Message-ID: <83eeuyr0vd.fsf@gnu.org> (raw)
In-Reply-To: <20200212073922.GA2812@localhost> (message from Henrik Grimler on Wed, 12 Feb 2020 08:39:58 +0100)
> Date: Wed, 12 Feb 2020 08:39:58 +0100
> From: Henrik Grimler <henrik@grimler.se>
>
> ../configure --enable-checking=yes,glyphs \
> --enable-check-lisp-object-type \
> --without-makeinfo \
> --without-selinux \
> --prefix /data/data/com.termux/files/usr/local \
> CFLAGS="-O0 -g3 -gdwarf-4"
> ```
>
> but building the emacs-27 branch (commit 06c302d) this fails with:
>
> ```
> [...]
> Loading /data/data/com.termux/files/home/projects/emacs/lisp/emacs-lisp/syntax.el (source)...
> Loading /data/data/com.termux/files/home/projects/emacs/lisp/font-lock.el (source)...
> Loading /data/data/com.termux/files/home/projects/emacs/lisp/jit-lock.el (source)...
>
> ../../src/fns.c:2856: Emacs fatal error: assertion failed: !FIXNUM_OVERFLOW_P (lisp_h_make_fixnum_n)
This would mean that the values returned by getloadavg on that system
are preposterously large. Can you run the offending command under a
debugger, put a breakpoint on line 2856 of fns.c, and see what values
you get in the load_ave[] array?
> This (as well as the segfault) happens both if compiling with clang 9.0.1 and gcc 9.2.0.
> I get a warning earlier multiple times that might be related:
>
> ```
> [...]
> CC dispnew.o
> In file included from ../../src/dispnew.c:29:
> In file included from ../../src/termchar.h:23:
> ../../src/dispextern.h:1917:36: warning: signed shift result (0x3FFFFC00000) requires 43 bits to represent, but 'EMACS_INT' (aka 'int') only has 32 bits [-Wshift-overflow]
> ? ((EMACS_INT) MAX_FACE_ID << CHARACTERBITS) | MAX_CHAR
> ~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~~~~
> 1 warning generated.
I think this warning is bogus, since if your EMACS_INT is not wide
enough to hold MAX_FACE_ID shifted left by 8 bits, the code will not
do that.
> If I remove --enable-checking=yes,glyphs it builds (I am sending this
> bug report from that build) but gets segmentation faults every now and
> then. Easiest way to trigger it is to scroll up and down in some file,
> but it still happens randomly, maybe after 200 lines, maybe after 10
> 000.
Can you show a backtrace from the segfault?
next prev parent reply other threads:[~2020-02-13 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 7:39 bug#39577: 27.0.60; Assertion failed during compilation Henrik Grimler
2020-02-13 14:57 ` Eli Zaretskii [this message]
2020-02-13 19:00 ` Henrik Grimler
2020-02-13 19:23 ` Eli Zaretskii
2020-02-13 20:04 ` Henrik Grimler
2020-02-17 20:53 ` Paul Eggert
2020-02-18 15:49 ` Henrik Grimler
2020-09-01 17:25 ` Stefan Kangas
2020-10-01 19:09 ` 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=83eeuyr0vd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39577@debbugs.gnu.org \
--cc=henrik@grimler.se \
/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).