[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#28308: Build failure on FreeBSD/aarch64

From: Gergely Czuczy
Subject: bug#28308: Build failure on FreeBSD/aarch64
Date: Mon, 11 Sep 2017 21:57:47 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

On 2017. 09. 11. 19:17, Eli Zaretskii wrote:
Cc: address@hidden, address@hidden
From: Gergely Czuczy <address@hidden>
Date: Mon, 11 Sep 2017 19:12:12 +0200

That's a call to delete_terminal, which doesn't appear in your
backtrace, and doesn't call xpalloc, either.  So thanks, but I'm still
confused.  Are you sure this is an unoptimized build?  Is it possible
that we are looking at LLDB bug?
It's the lldb debug, right. And I'm sure it's an unoptimized build, I've
went back and checked the build flags:
cc -Demacs  -I. -I. -I../lib -I../lib
-I/usr/local/include/libxml2             -MMD -MF deps/.d -MP
-Wno-switch -Wno-pointer-sign -Wno-string-plus-int
-Wno-unknown-attributes -Wno-initializer-overrides
-Wno-tautological-constant-out-of-range-compare -O0 -g
-fno-strict-aliasing  -Wl,-znocombreloc  (...)

If that helps, I can create a qemu VM with this fbsd build, and give you
the image.
Would it be possible for you to install GDB, and then repeat the same
experiment under GDB?
Unfortunately that won't work:
# make install
===>  gdb-8.0_1 is only for amd64 armv6 i386 mips powerpc powerpc64, while
you are running aarch64.

However, I've found that clang is able to tune the debug info for lldb with -glldb. Let me try that. It might take a bit of time, and it's 10pm here, so might get back with that tomorrow.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]