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 18:31:35 +0300 [thread overview]
Message-ID: <83tw09s148.fsf@gnu.org> (raw)
In-Reply-To: <b01f7b9b-e951-e40c-c538-39e50bccc4f2@harmless.hu> (message from Gergely Czuczy on Mon, 11 Sep 2017 17:10:39 +0200)
> Cc: npostavs@users.sourceforge.net, 28308@debbugs.gnu.org
> From: Gergely Czuczy <gergely.czuczy@harmless.hu>
> Date: Mon, 11 Sep 2017 17:10:39 +0200
>
> >> bootstrap-emacs`xnrealloc(pa=0x000000000019ae38, nitems=42949672960,
> >> item_size=281474976703896) at alloc.c:939
> >> frame #2: 0x000000000022e208
> >> bootstrap-emacs`xpalloc(pa=0x0000000000000000,
> >> nitems=0x0000000041b1797f, nitems_incr_min=1683000,
> >> nitems_max=42949672960, item_size=281474976703896) at alloc.c:0
> >> frame #3: 0x0000000000168214
> >> bootstrap-emacs`delete_tty(terminal=0x3276551740f23ac5) at term.c:4463
> >> frame #4: 0x0000000000040190 bootstrap-emacs`__start + 376
> >> frame #5: 0x0000000040390018 ld-elf.so.1`.rtld_start at rtld_start.S:41
> >> (lldb)
> > I don't understand how can this be. Can you go to frame #3, in
> > delete_tty, and show what line of C code there allegedly calls
> > xpalloc?
> Sure, here it is:
> https://github.com/emacs-mirror/emacs/blob/f44184f/src/term.c#L4463
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?
next prev parent reply other threads:[~2017-09-11 15:31 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 [this message]
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
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=83tw09s148.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).