From: Eli Zaretskii <eliz@gnu.org>
To: Henrik Grimler <hgrimler@kth.se>
Cc: 39577@debbugs.gnu.org
Subject: bug#39577: 27.0.60; Assertion failed during compilation
Date: Thu, 13 Feb 2020 21:23:38 +0200 [thread overview]
Message-ID: <835zgaqojp.fsf@gnu.org> (raw)
In-Reply-To: <20200213190016.GA11739@localhost> (message from Henrik Grimler on Thu, 13 Feb 2020 20:00:16 +0100)
> Date: Thu, 13 Feb 2020 20:00:16 +0100
> From: Henrik Grimler <hgrimler@kth.se>
> Cc: 39577@debbugs.gnu.org
>
> > > ../../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?
>
> It seems to be preposterously small:
>
> ```
> Breakpoint 2, Fload_average (use_floats=XIL(0)) at ../../src/fns.c:2856
> 2856 ? make_fixnum (100.0 * load_ave[loads])
> (gdb) print load_ave
> $1 = {2.8900000000000001, 2.8752811112650786e-312, 2.7799999999999998}
> ```
>
> This android version does not have getloadavg (so I guess
> lib/getloadavg.c is used instead?)
Looks like a bug in getloadavg, but you should be fine replacing that
small value with zero.
> > Can you show a backtrace from the segfault?
>
> After loading gdbinit from emacs src, starting emacs and scrolling up
> and down a file a couple of times it crashes with:
>
> ```
> Program received signal SIGSEGV, Segmentation fault.
> 0xb6995228 in sigsetjmp () from /system/lib/libc.so
> ```
>
> A backtrace then unfortunately only shows:
>
> ```
> #0 0xb6995228 in sigsetjmp () from /system/lib/libc.so
> #1 0x62e31f80 in ?? ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Sounds like sigsetjmp is buggy on that platform?
> It also seems that the segfault does not happen if running inside
> tmux.
Does "inside tmux" mean you run a -nw session?
next prev parent reply other threads:[~2020-02-13 19:23 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
2020-02-13 19:00 ` Henrik Grimler
2020-02-13 19:23 ` Eli Zaretskii [this message]
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=835zgaqojp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39577@debbugs.gnu.org \
--cc=hgrimler@kth.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).