all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gergely Czuczy <gergely.czuczy@harmless.hu>, 28308@debbugs.gnu.org
Subject: bug#28308: Build failure on FreeBSD/aarch64
Date: Tue, 24 Oct 2017 14:43:09 -0400	[thread overview]
Message-ID: <CAM-tV--7NYCG6RGsyckHLFumAjt46krBc1pMqF0c2RbUYcmFGg@mail.gmail.com> (raw)
In-Reply-To: <83wp3qcn5k.fsf@gnu.org>

On Fri, Oct 20, 2017 at 3:07 AM, Eli Zaretskii <eliz@gnu.org> wrote:

>> * 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

> 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?

The faulting address is XFLOAT(f):

static void
XFLOAT_INIT (Lisp_Object f, double n)
{
  XFLOAT (f)->u.data = n;
}

'f' is 'val' in make_float. I added a fprintf(stderr, "%p\n",
XFLOAT(val)) before the XFLOAT_INIT call, the address which was ok
with temacs triggers SIGSEGV in bootstrap-emacs.
It seems that the memory pointer to by float_block->floats becomes
invalid following the dumping process.

By the way, when I delete bootstrap-emacs and redump, the faulting
address changes (although it's always of the form 0x4XXXXXXX).





  reply	other threads:[~2017-10-24 18:43 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
2017-10-24 18:43                                 ` Noam Postavsky [this message]
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=CAM-tV--7NYCG6RGsyckHLFumAjt46krBc1pMqF0c2RbUYcmFGg@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=28308@debbugs.gnu.org \
    --cc=eliz@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.