From: David Caldwell <david@porkrind.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 18505@debbugs.gnu.org
Subject: bug#18505: 24.3.93; intermittent unexec failures when building on Mac OS X 10.10 beta, Xcode 6.0
Date: Sat, 20 Sep 2014 11:31:10 -0700 [thread overview]
Message-ID: <541DC7EE.6080309@porkrind.org> (raw)
In-Reply-To: <D971C423-D526-4DC3-8CA5-23CD9A88C11D@swipnet.se>
[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]
On 9/20/14 8:31 AM, Jan Djärv wrote:
> Hello.
>
> 19 sep 2014 kl. 06:13 skrev David Caldwell <david@porkrind.org>:
>
>> Hello,
>>
>> I tried to build the latest pretest on Mac OS X Yosemite Beta with the
>> new Xcode 6.0 (GM) tools and ran into this error during the unexec step:
>>
>> unexec: not enough room for load commands for new __DATA segments
>
> Does it happen all the time or just some times?
It depends on 2 variables: the number of load commands that need to be
added (num_unexec_regions) and text_seg_lowest_offset.
num_unexec_regions jumps around a lot, doing "make clean && make" over
and over it'll be different every time. Somewhere between 12 and 34.
text_seg_lowest_offset seems more stable, but it still changes. When I
first unpacked the tarball and compiled, text_seg_lowest_offset was very
low: 0x17c0. This stayed constant for about an hour while I was
debugging this (adding debug prints) and then mysteriously jumped up to
0x24f0 at which point the unexec started succeeding without the change
to headerpad_extra.
I just unpacked a clean pretest source directory and
text_seg_lowest_offset was 0x17a0 and unexec failed.
Doing
(make clean && make) 2>&1 | grep "Lowest offset of all sections"
over and over gives me:
Lowest offset of all sections in __TEXT segment: 0x17a0
Lowest offset of all sections in __TEXT segment: 0x17a0
Lowest offset of all sections in __TEXT segment: 0x17a0
Lowest offset of all sections in __TEXT segment: 0x17a0
Lowest offset of all sections in __TEXT segment: 0x17a0
Lowest offset of all sections in __TEXT segment: 0x17a0
Though one of those times it didn't fail (presumably because
num_unexec_regions was low enough).
-David
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2014-09-20 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 4:13 bug#18505: 24.3.93; intermittent unexec failures when building on Mac OS X 10.10 beta, Xcode 6.0 David Caldwell
2014-09-20 15:31 ` Jan Djärv
2014-09-20 18:31 ` David Caldwell [this message]
2014-09-21 9:15 ` Jan Djärv
2014-09-21 18:07 ` David Caldwell
2014-09-21 20:37 ` Jan Djärv
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=541DC7EE.6080309@porkrind.org \
--to=david@porkrind.org \
--cc=18505@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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).