From: Henrik Grimler <henrik@grimler.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39577@debbugs.gnu.org
Subject: bug#39577: 27.0.60; Assertion failed during compilation
Date: Thu, 13 Feb 2020 21:04:30 +0100 [thread overview]
Message-ID: <20200213200430.GA18685@localhost> (raw)
In-Reply-To: <835zgaqojp.fsf@gnu.org>
> > > 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?
Could be? I have not seen any bug reports or similar issues for other
programs that seem related though, but android arm is fairly
rare these days. I am dreaming of finding a workaround on the emacs
side of things as I can not modify the system libraries (well not
easily anyways). I suppose I need to learn more about sigsetjmp and
friends to have a chance at that.
> > It also seems that the segfault does not happen if running inside
> > tmux.
>
> Does "inside tmux" mean you run a -nw session?
Yes, sorry for not being clear. I am running inside a terminal
emulator for android called termux, all programs are linked against
android's libc, bionic. Compilers and other tools needed for compiling
emacs are available, but there is no x11 so emacs can only be run in -nw
mode.
next prev parent reply other threads:[~2020-02-13 20:04 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
2020-02-13 20:04 ` Henrik Grimler [this message]
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=20200213200430.GA18685@localhost \
--to=henrik@grimler.se \
--cc=39577@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).