Re: Problem using .zerofill / -segaddr to create very large segments
Re: Problem using .zerofill / -segaddr to create very large segments
- Subject: Re: Problem using .zerofill / -segaddr to create very large segments
- From: Jay Reynolds Freeman <email@hidden>
- Date: Tue, 22 Sep 2009 22:25:42 -0700
And now I report a fascinating experiment: See my posting dated
10:12 PM PDT 22 September for context.
I had been successfully running with a .s file containing quantity
160 of 1-GByte ".zerofill" lines, and failing when I added one
more such line.
So, I changed my file so that each .zerofill was for 1.5 GByte --
changed 0x40000000 to 0x60000000 in 160 places. It built and
ran fine, and the output of vmmap shows a 240 GByte chunk properly
mapped! That is enough memory for me for now. (That is just
as well, because .zerofill appears to accept only SIGNED 32-bit
numbers -- 0x80000000 causes an error about a negative section
size...)
Evidently the problem is not with the total size of the segment,
but with the number of .zerofills.
I suspect it is time for me to file some kind of bug report.
With this information and the content of my previous post, can
Terry or Greg suggest any more useful experiments, or any
suggestions for what to file such a report against?
I keep forgetting to thank you all for assistance; thanks very much.
-- Jay Reynolds Freeman
---------------------
email@hidden
http://web.mac.com/jay_reynolds_freeman (personal web site)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden