From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Gergely Czuczy <gergely.czuczy@harmless.hu>
Cc: 28308@debbugs.gnu.org
Subject: bug#28308: Build failure on FreeBSD/aarch64
Date: Thu, 19 Oct 2017 19:39:11 -0400 [thread overview]
Message-ID: <8760bag128.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CAM-tV-9jsdgWZx3inLELQ60A_25VbGdcKWN9PTDKou1ycPm-Xw@mail.gmail.com> (Noam Postavsky's message of "Wed, 20 Sep 2017 15:29:15 -0400")
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> (lldb) disassemble --pc
> bootstrap-emacs`__start:
> -> 0x40180 <+360>: mov w0, w21
> 0x40184 <+364>: mov x1, x20
> 0x40188 <+368>: mov x2, x19
> 0x4018c <+372>: bl 0x16742c ; tty_menu_display + 132 at term.c:2817
> I think that means that tty_menu_display is getting called from
> __start, which should not be possible?!
It seems that the debug info show by lldb is bogus, it shows two
locations for tty_menu_display (see attached).
[-- Attachment #2: excerpts from an lldb session --]
[-- Type: text/plain, Size: 2499 bytes --]
(lldb) expr main
(int (*)(int, char **)) $0 = 0x0000000000167474
(lldb) disassemble -s 0x167474 -e (0x167474+16)
bootstrap-emacs`main:
bootstrap-emacs[0x167474] <+0>: str x28, [sp, #-0x20]!
bootstrap-emacs[0x167478] <+4>: stp x29, x30, [sp, #0x10]
bootstrap-emacs[0x16747c] <+8>: add x29, sp, #0x10 ; =0x10
bootstrap-emacs[0x167480] <+12>: sub sp, sp, #0x1f0 ; =0x1f0
(lldb) disassemble -p -b
bootstrap-emacs`tty_menu_display:
-> 0x167474 <+128>: 0xf81e0ffc str x28, [sp, #-0x20]!
0x167478 <+132>: 0xa9017bfd stp x29, x30, [sp, #0x10]
0x16747c <+136>: 0x910043fd add x29, sp, #0x10 ; =0x10
0x167480 <+140>: 0xd107c3ff sub sp, sp, #0x1f0 ; =0x1f0
(lldb) expr tty_menu_display
(void (*)(tty_menu *, int, int, int, int *, int, int, int, bool)) $1 = 0x00000000001573f4
(lldb) disassemble -n tty_menu_display
bootstrap-emacs`tty_menu_display:
0x1573f4 <+0>: sub sp, sp, #0xa0 ; =0xa0
0x1573f8 <+4>: stp x29, x30, [sp, #0x90]
0x1573fc <+8>: add x29, sp, #0x90 ; =0x90
0x157400 <+12>: ldrb w8, [x29, #0x10]
0x157404 <+16>: adrp x9, 1497
0x157408 <+20>: add x9, x9, #0x998 ; =0x998
0x15740c <+24>: stur x0, [x29, #-0x8]
0x157410 <+28>: stur w1, [x29, #-0xc]
[...]
0x1577d4 <+992>: bl 0x43498
0x1577d8 <+996>: ldp x29, x30, [sp, #0x90]
0x1577dc <+1000>: add sp, sp, #0xa0 ; =0xa0
0x1577e0 <+1004>: ret
bootstrap-emacs`tty_menu_display:
0x1673f4 <+0>: add sp, sp, #0xa0 ; =0xa0
0x1673f8 <+4>: ret
0x1673fc <+8>: sub sp, sp, #0x20 ; =0x20
0x167400 <+12>: stp x29, x30, [sp, #0x10]
0x167404 <+16>: add x29, sp, #0x10 ; =0x10
0x167408 <+20>: adrp x8, 1469
0x16740c <+24>: add x8, x8, #0x470 ; =0x470
0x167410 <+28>: stur w0, [x29, #-0x4]
0x167414 <+32>: ldursw x9, [x29, #-0x4]
[...]
0x167468 <+116>: bl 0x2921d8 ; Fapply + 6324 at eval.c:2364
0x16746c <+120>: ldp x29, x30, [sp], #0x10
0x167470 <+124>: ret
-> 0x167474 <+128>: str x28, [sp, #-0x20]!
0x167478 <+132>: stp x29, x30, [sp, #0x10]
0x16747c <+136>: add x29, sp, #0x10 ; =0x10
0x167480 <+140>: sub sp, sp, #0x1f0 ; =0x1f0
0x167484 <+144>: mov w8, wzr
0x167488 <+148>: adrp x9, 1500
[-- Attachment #3: Type: text/plain, Size: 894 bytes --]
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
This is from revision [1: 35c893ddaf], configured with
'CFLAGS=-O0 -glldb -DUNEXELF_DEBUG=1' '--without-all'
[1: 35c893ddaf]: 2017-09-12 11:08:00 -0400
Move gensym to core Elisp
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=35c893ddaf21b93677850a69709b59630bb0feb7
next prev parent reply other threads:[~2017-10-19 23:39 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 [this message]
2017-10-20 7:07 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760bag128.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=28308@debbugs.gnu.org \
--cc=gergely.czuczy@harmless.hu \
/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.