unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42891@debbugs.gnu.org
Subject: bug#42891: 28.0.50; High Sierra Macos build failure
Date: Sun, 16 Aug 2020 20:28:49 +0200 (CEST)	[thread overview]
Message-ID: <20200816182846.GB70356@breton.holly.idiocy.org> (raw)
In-Reply-To: <87k0xyvb0m.fsf@gnus.org>

On Sun, Aug 16, 2020 at 05:57:45PM +0200, Lars Ingebrigtsen wrote:
> 
> I set up a bunch of VMs with different Macos versions, and Emacs builds
> fine on Mojave and Catalina, but not High Sierra (which is the oldest of
> the supported Macos versions).
> 
> It fails with
> 
> /Library/Developer/CommandLineTools/usr/bin/make -C ../lisp update-subdirs
> cp -f temacs bootstrap-emacs
> rm -f bootstrap-emacs.pdmp
> ./temacs --batch  -l loadup --temacs=pbootstrap
> make[2]: *** [bootstrap-emacs.pdmp] Segmentation fault: 11 (core dumped)
> make[1]: *** [src] Error 2
> make: *** [bootstrap] Error 2
> 
> Larss-iMac:trunk larsi$ gcc --version
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 10.0.0 (clang-1000.10.44.4)
> Target: x86_64-apple-darwin17.7.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
> 
> I don't know whether we care about this system or not?  Is that a
> too-old clang version for us to worry about this?

As far as I'm aware we should be able to build on anything back to
10.6, so it should work fine on High Sierra. I've never come across
this problem, though.

> I'm completely unfamiliar with how lldb works...  this backtrace doesn't
> looke very useful?
> 
> Larss-iMac:trunk larsi$ lldb src/temacs --core /cores/core.36630 
> (lldb) target create "src/temacs" --core "/cores/core.36630"
> warning: (x86_64) /cores/core.36630 load command 200 LC_SEGMENT_64 has a fileoff + filesize (0x4ead2000) that extends beyond the end of the file (0x4ead1000), the segment will be truncated to match
> warning: (x86_64) /cores/core.36630 load command 201 LC_SEGMENT_64 has a fileoff (0x4ead2000) that extends beyond the end of the file (0x4ead1000), ignoring this section
> Core file '/cores/core.36630' (x86_64) was loaded.
> (lldb) bt all
> * thread #1, stop reason = signal SIGSTOP
>   * frame #0: 0x00007fff50f81993 libsystem_platform.dylib`_platform_memmove$VARIANT$Base + 1875
>   thread #2, stop reason = signal SIGSTOP
>     frame #0: 0x00007fff50dc028a libsystem_kernel.dylib`__workq_kernreturn + 10
>     frame #1: 0x00007fff50f8720e libsystem_pthread.dylib`_pthread_wqthread + 1552
>     frame #2: 0x00007fff50f86be9 libsystem_pthread.dylib`start_wqthread + 13
>   thread #3, stop reason = signal SIGSTOP
>     frame #0: 0x00007fff50dc028a libsystem_kernel.dylib`__workq_kernreturn + 10
>     frame #1: 0x00007fff50f87009 libsystem_pthread.dylib`_pthread_wqthread + 1035
>     frame #2: 0x00007fff50f86be9 libsystem_pthread.dylib`start_wqthread + 13

No, it looks like it crashed before it even got to our code as I would
expect to see main() or something listed in thread #1's backtrace. My
first suspicion would be there's something wrong with the build
environment. *grasping at straws* It didn't run out of disk space or
something?
-- 
Alan Third





  reply	other threads:[~2020-08-16 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16 15:57 bug#42891: 28.0.50; High Sierra Macos build failure Lars Ingebrigtsen
2020-08-16 18:28 ` Alan Third [this message]
2020-08-16 18:33   ` Lars Ingebrigtsen
2020-08-16 19:35   ` Lars Ingebrigtsen

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=20200816182846.GB70356@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=42891@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).