Re: Adventure - the answer to what went wrong?

Dan Olson
2002-12-12T20:27:00Z

Also, the file size is 84k, but that doesn't mean that the code segment is
going to be more than 64k, does it? Does the whole file get loaded into
memory and executed, or can there be other "stuff" in that file besides
executable code that may not get loaded into the code segment? I haven't
messed with this stuff in a while, so I don't remember :)

Dan

On Thu, 12 Dec 2002, Alan Cox wrote:

> On Thu, 2002-12-12 at 19:11, Richard Wallman wrote:
> > I put forward the theory that it fails because the two strings are not
> > in the same 64Kb segment. The reason no-one has found this problem
> > before is that so far all of the binaries have been <64Kb in size.
>
> ELKS only supports a max of 64K code / 64K data per app...
>
>
>
> Alan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>