From: Andy Wingo <wingo@pobox.com>
To: John Ralls <jralls@ceridwen.us>
Cc: 19372@debbugs.gnu.org
Subject: bug#19372: Compile Failure on OS X 10.10 (Yosemite)
Date: Wed, 22 Jun 2016 21:25:42 +0200 [thread overview]
Message-ID: <87d1n9rpop.fsf@pobox.com> (raw)
In-Reply-To: <52AF5B85-3F51-4B28-80E6-6B845E38F8D2@ceridwen.us> (John Ralls's message of "Sat, 13 Dec 2014 11:28:27 -0800")
Hi John,
Did you find out what was the deal here? A very strange error!
Andy
On Sat 13 Dec 2014 20:28, John Ralls <jralls@ceridwen.us> writes:
> Attempting to build Guile 2.0.11 on OS X 10.10 with Xcode 6.1.1 and MacOS10.10.sdk fails:
>> /bin/sh: line 1: 53480 Segmentation fault: 11 GUILE_INSTALL_LOCALE=1
>> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guild compile
>> --target="x86_64-apple-darwin14.0.0" -Wunbound-variable
>> -Warity-mismatch -Wformat -L
>> "/Users/john/Development/Gnucash-Build/Gnucash-master-git-64/src/guile-2.0.11/module"
>> -L
>> "/Users/john/Development/Gnucash-Build/Gnucash-master-git-64/src/guile-2.0.11/module"
>> -L
>> "/Users/john/Development/Gnucash-Build/Gnucash-master-git-64/src/guile-2.0.11/guile-readline"
>> -o "srfi/srfi-27.go" "srfi/srfi-27.scm"
>> make[2]: *** [srfi/srfi-27.go] Error 139
>> make[2]: *** Waiting for unfinished jobs....
>> wrote `srfi/srfi-35.go'
>> wrote `srfi/srfi-37.go'
>> /bin/sh: line 1: 53393 Segmentation fault: 11 GUILE_INSTALL_LOCALE=1
>> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guild compile
>> --target="x86_64-apple-darwin14.0.0" -Wunbound-variable
>> -Warity-mismatch -Wformat -L
>> "/Users/john/Development/Gnucash-Build/Gnucash-master-git-64/src/guile-2.0.11/module"
>> -L
>> "/Users/john/Development/Gnucash-Build/Gnucash-master-git-64/src/guile-2.0.11/module"
>> -L
>> "/Users/john/Development/Gnucash-Build/Gnucash-master-git-64/src/guile-2.0.11/guile-readline"
>> -o "srfi/srfi-19.go" "srfi/srfi-19.scm”
>
> It succeeds with MacOSX10.9.sdk.
>
> The crash reports:
>
>> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
>> Exception Codes: EXC_I386_GPFLT
>>
>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
>> 0 libdyld.dylib 0x00007fff91d46432 stack_not_16_byte_aligned_error + 0
>>
>> Thread 0 crashed with X86 Thread State (64-bit):
>> rax: 0x0280000000000000 rbx: 0x0000000000000001 rcx: 0x00000000ffffffc6 rdx: 0x00007fff5dcb88a0
>> rdi: 0xa000000000000000 rsi: 0x00007fff5dcb88a0 rbp: 0x0000000000000000 rsp: 0x00007fff5dcb8728
>> r8: 0xa000000000000000 r9: 0x00007fde73000010 r10: 0x00000000000024f8 r11: 0x000000010231d118
>> r12: 0x0000000000000000 r13: 0x0000000000000001 r14: 0x0000000000000001 r15: 0x00007fde73000000
>> rip: 0x00007fff91d46432 rfl: 0x0000000000010202 cr2: 0x00000001022e78c0
>>
>> Logical CPU: 2
>> Error Code: 0x00000000
>> Trap Number: 13
>
> and:
>
>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>>
>> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
>> Exception Codes: EXC_I386_GPFLT
>>
>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
>> 0 libdyld.dylib 0x00007fff91d46432 stack_not_16_byte_aligned_error + 0
>>
>> Thread 0 crashed with X86 Thread State (64-bit):
>> rax: 0x02625a0000000000 rbx: 0x0000000000000001 rcx: 0x00000000ffffffc6 rdx: 0x00007fff566d68a0
>> rdi: 0x9896800000000000 rsi: 0x00007fff566d68a0 rbp: 0x0000000000000000 rsp: 0x00007fff566d6728
>> r8: 0x9896800000000000 r9: 0x00007fa899d00190 r10: 0x00000000000024f8 r11: 0x00000001098f9118
>> r12: 0x0000000000000000 r13: 0x0000000000000001 r14: 0x0000000000000001 r15: 0x00007fa899d00180
>> rip: 0x00007fff91d46432 rfl: 0x0000000000010202 cr2: 0x00000001098c38c0
>>
>> Logical CPU: 8
>> Error Code: 0x00000000
>> Trap Number: 13
>
> Debugging with gdb shows a smashed stack after the segfault, so the stack_not_16_byte_aligned_error is probably spurious.
>
> Regards,
> John Ralls
next prev parent reply other threads:[~2016-06-22 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 19:28 bug#19372: Compile Failure on OS X 10.10 (Yosemite) John Ralls
2014-12-13 22:07 ` Hans Aberg
2016-06-22 19:25 ` Andy Wingo [this message]
2016-06-22 20:58 ` John Ralls
2016-06-22 21:35 ` Andy Wingo
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=87d1n9rpop.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=19372@debbugs.gnu.org \
--cc=jralls@ceridwen.us \
/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).