From: Dan Kegel <dank@kegel.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: guile 2.2.3 crashing on osx 10.11?
Date: Sun, 31 Dec 2017 17:53:59 -0800 [thread overview]
Message-ID: <CAPF-yObmuPOk6BWQpj1i+2nNwr0cBAPkSMeqDbOiebjZXSkmEg@mail.gmail.com> (raw)
In-Reply-To: <DCEC82C4-3765-45AC-B8DE-1511B52D83FD@gmail.com>
On Sat, Dec 30, 2017 at 3:31 PM, Matt Wette <matt.wette@gmail.com> wrote:
>> On Dec 30, 2017, at 2:32 PM, Dan Kegel <dank@kegel.com> wrote:
>> osx 10.11, though, crashes when I just evaluate (display (version)),
>> or sometimes while building.
>
> I have not seen that on macOS before, but previously ran into other issues. This may help to chase it down:
>
> build with use
> CFLAGS=-g LDFLAGS=-g ./configure --disable-shared --prefix=/opt/local
>
> in meta/gdb-uninstalled-guile, change:
> gdb --args ${top_builddir}/libguile/guile "$@"
> to
> lldb -- ${top_builddir}/libguile/guile "$@"
>
> and, IIRC, run meta/gdb-installed-guile
Thanks. Also had to do
sudo /usr/sbin/DevToolsSecurity --enable
Here's a backtrace:
* thread #1: tid = 0x1628f8, 0x00000001003e95be
libgmp.10.dylib`__gmpn_mul_1 + 94, queue = 'com.apple.main-thread',
stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
frame #0: 0x00000001003e95be libgmp.10.dylib`__gmpn_mul_1 + 94
libgmp.10.dylib`__gmpn_mul_1:
-> 0x1003e95be <+94>: mulxq (%rsi), %rbx, %rax
Guess what? This machine is a i7-3720QM (in a Macbook Pro 9,1), which
doesn't support MULX. (It's 2012 Ivy Bridge, which is just
pre-Haswell.)
$ gobjdump -d libgmp.dylib | grep mulx
confirms the presence of the mulx instruction.
So my gmp was built wrong for this machine. (There was a related
bugfix for low-end cpus in gmp 6.1.1, but I've got 6.1.2, and no
low-end cpus.)
Bit of a mystery, then, but nothing to do with guile.
- Dan
next prev parent reply other threads:[~2018-01-01 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 22:32 guile 2.2.3 crashing on osx 10.11? Dan Kegel
2017-12-30 23:31 ` Matt Wette
2018-01-01 1:53 ` Dan Kegel [this message]
2018-01-01 18:25 ` Dan Kegel
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPF-yObmuPOk6BWQpj1i+2nNwr0cBAPkSMeqDbOiebjZXSkmEg@mail.gmail.com \
--to=dank@kegel.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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.
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).