GNU bug report logs - #39577
27.0.60; [android 32 bit arm] Assertion failed during compilation

Previous Next

Package: emacs;

Reported by: Henrik Grimler <henrik <at> grimler.se>

Date: Wed, 12 Feb 2020 15:32:02 UTC

Severity: normal

Found in version 27.0.60

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Henrik Grimler <hgrimler <at> kth.se>
Cc: 39577 <at> debbugs.gnu.org
Subject: bug#39577: 27.0.60; Assertion failed during compilation
Date: Thu, 13 Feb 2020 21:23:38 +0200
> Date: Thu, 13 Feb 2020 20:00:16 +0100
> From: Henrik Grimler <hgrimler <at> kth.se>
> Cc: 39577 <at> 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?




This bug report was last modified 4 years and 231 days ago.

Previous Next


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