From: Eli Zaretskii <eliz@gnu.org>
To: Barry Warsaw <barry@python.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 25.1 build failures on Ubuntu arm64
Date: Wed, 29 Mar 2017 18:03:14 +0300 [thread overview]
Message-ID: <838tno6s7h.fsf@gnu.org> (raw)
In-Reply-To: <20170328203040.0a1e0b98@subdivisions.wooz.org> (message from Barry Warsaw on Tue, 28 Mar 2017 20:30:40 -0400)
> From: Barry Warsaw <barry@python.org>
> Date: Tue, 28 Mar 2017 20:30:40 -0400
>
> I'm not sure how much of this email will be actionable, but I wanted to at
> least let y'all know about a problem we've seen building Emacs 25.1 on Ubuntu
> 17.04 arm64.
Did this configuration build correctly with Emacs 24.5?
> In any case, for several weeks now we've seen Emacs segfault on arm64 builders
> consistently in what I think are the CEDET tests. The full traceback, when
> we've been able to capture it, is here:
>
> https://launchpadlibrarian.net/302409391/gdb-bt-full.txt
I see this there:
#5 handle_sigsegv (sig=11, siginfo=<optimized out>, arg=<optimized out>) at sysdep.c:1695
fatal = <optimized out>
#6 <signal handler called>
No symbol table info available.
#7 unchain_marker (marker=marker@entry=0x130ad18) at marker.c:605
tail = <optimized out>
prev = 0x676e696e6e6967e5
b = 0x130acf0
#8 0x00000000005334a4 in free_marker (marker=marker@entry=19967257) at alloc.c:3850
No locals.
The value of 'prev' in frame #7 looks garbled: it's ASCII text
"ginning", probably was "beginning" at some point. This might
indicate memory corruption, either some dynamically allocated memory
or the stack got smashed.
Does your build compile ralloc.c? If so, could you try configuring
with REL_ALLOC=no?
> and the bug that tracks this is here:
>
> https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474
That bug mentions several fixed done by Debian; did you try them?
next prev parent reply other threads:[~2017-03-29 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 0:30 Emacs 25.1 build failures on Ubuntu arm64 Barry Warsaw
2017-03-29 15:03 ` Eli Zaretskii [this message]
2017-03-29 20:46 ` Barry Warsaw
2017-03-29 21:57 ` Barry Warsaw
2017-08-01 14:55 ` Rob Browning
2017-08-04 12:26 ` Byung-Hee HWANG (황병희, 黃炳熙)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838tno6s7h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=barry@python.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.