From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <13426df10707031105n508a5faflf7c8d8fc65c0bc20@mail.gmail.com>
Date: Tue,  3 Jul 2007 11:05:10 -0700
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] executable memory map
In-Reply-To: <cccb85fdd879db4cb9fd4d010671d2c1@quintile.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <cccb85fdd879db4cb9fd4d010671d2c1@quintile.net>
Topicbox-Message-UUID: 8fd0a0e2-ead2-11e9-9d60-3106f5b1d025

On 7/2/07, Steve Simon <steve@quintile.net> wrote:

>         2/ Does the a.out file contain padding to ensure .data starts on a 4k boundry
>         or does the kernel's loader move .data (using memcpy() or MMU mapping)?

loader for a.out has to align the .data segment via move -- it is not
aligned in the file.

ron