From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: gergely.czuczy@harmless.hu, 28308@debbugs.gnu.org
Subject: bug#28308: Build failure on FreeBSD/aarch64
Date: Fri, 20 Oct 2017 10:07:51 +0300 [thread overview]
Message-ID: <83wp3qcn5k.fsf@gnu.org> (raw)
In-Reply-To: <8760bag128.fsf@users.sourceforge.net> (message from Noam Postavsky on Thu, 19 Oct 2017 19:39:11 -0400)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, 28308@debbugs.gnu.org
> Date: Thu, 19 Oct 2017 19:39:11 -0400
>
> It seems that the debug info show by lldb is bogus, it shows two
> locations for tty_menu_display (see attached).
Maybe that function was inlined?
> Here is a backtrace from running 'lldb -- ./bootstrap-emacs -Q -batch',
> with source locations generated by 'addr2line -e ./bootstrap-emacs -f -i -p'.
>
> * thread #1, name = 'bootstrap-emacs', stop reason = signal SIGSEGV: invalid address (fault address: 0x41626d78)
> 0x000000000022810c XFLOAT_INIT at /root/emacs/src/alloc.c:543
> 0x0000000000227eb0 make_float at /root/emacs/src/alloc.c:2667
> 0x000000000022de24 init_alloc at /root/emacs/src/alloc.c:7481
> 0x000000000016825c main at /root/emacs/src/emacs.c:1251
> 0x0000000000040190 __start at /tank/rpi3/src/lib/csu/aarch64/crt1.c:84
> 0x0000000040390018 ?? at ??:0
Can you disassemble XFLOAT_INIT and tell which part of it caused the
segfault, and why? In particular, what is the relation of the
faulting address 0x41626d78 and the C source?
next prev parent reply other threads:[~2017-10-20 7:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 16:34 bug#28308: Build failure on FreeBSD/aarch64 Gergely Czuczy
2017-08-31 16:47 ` Glenn Morris
2017-08-31 17:02 ` Gergely Czuczy
2017-09-02 3:13 ` npostavs
2017-09-04 12:32 ` Gergely Czuczy
2017-09-08 23:52 ` npostavs
2017-09-09 5:01 ` Gergely Czuczy
2017-09-09 7:07 ` Eli Zaretskii
2017-09-11 6:07 ` npostavs
2017-09-11 7:26 ` Gergely Czuczy
2017-09-11 14:45 ` Eli Zaretskii
2017-09-11 15:10 ` Gergely Czuczy
2017-09-11 15:31 ` Eli Zaretskii
2017-09-11 17:12 ` Gergely Czuczy
2017-09-11 17:17 ` Eli Zaretskii
2017-09-11 19:57 ` Gergely Czuczy
2017-09-11 20:33 ` Gergely Czuczy
2017-09-12 5:22 ` npostavs
2017-09-12 5:57 ` Gergely Czuczy
2017-09-12 14:59 ` Eli Zaretskii
2017-09-12 15:13 ` Gergely Czuczy
2017-09-20 5:51 ` Gergely Czuczy
2017-09-20 19:29 ` Noam Postavsky
2017-10-19 23:39 ` Noam Postavsky
2017-10-20 7:07 ` Eli Zaretskii [this message]
2017-10-24 18:43 ` Noam Postavsky
2017-10-31 17:31 ` Noam Postavsky
2017-10-31 20:21 ` Eli Zaretskii
2017-11-01 16:14 ` Gergely Czuczy
2017-11-01 16:51 ` Noam Postavsky
2017-11-01 18:27 ` Gergely Czuczy
2017-11-01 18:52 ` Noam Postavsky
2017-11-02 21:03 ` Gergely Czuczy
2017-11-04 23:14 ` Noam Postavsky
2017-11-05 18:10 ` Gergely Czuczy
2017-11-06 23:14 ` Noam Postavsky
2017-09-14 0:51 ` Paul Eggert
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=83wp3qcn5k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28308@debbugs.gnu.org \
--cc=gergely.czuczy@harmless.hu \
--cc=npostavs@users.sourceforge.net \
/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).