From: Eli Zaretskii <eliz@gnu.org>
To: Gergely Czuczy <gergely.czuczy@harmless.hu>
Cc: 28308@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#28308: Build failure on FreeBSD/aarch64
Date: Mon, 11 Sep 2017 20:17:15 +0300 [thread overview]
Message-ID: <83bmmhrw84.fsf@gnu.org> (raw)
In-Reply-To: <bd32eac4-fec0-b2d9-958d-84fce0eb8a79@harmless.hu> (message from Gergely Czuczy on Mon, 11 Sep 2017 19:12:12 +0200)
> Cc: npostavs@users.sourceforge.net, 28308@debbugs.gnu.org
> From: Gergely Czuczy <gergely.czuczy@harmless.hu>
> 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-compare
> -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?
next prev parent reply other threads:[~2017-09-11 17:17 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 [this message]
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
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=83bmmhrw84.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).