Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!ucsdhub!jack!man!nu3b2!rwhite
From: rwhite@nu3b2.UUCP (Robert C. White Jr.)
Newsgroups: comp.sys.amiga,comp.sys.atari.st,comp.sys.m6809
Subject: Re: True Multitasking, and shared code
Message-ID: <677@nu3b2.UUCP>
Date: Mon, 15-Jun-87 03:01:05 EDT
Article-I.D.: nu3b2.677
Posted: Mon Jun 15 03:01:05 1987
Date-Received: Sun, 21-Jun-87 06:33:57 EDT
References: <8706040024.AA10895@cogsci.berkeley.edu> <2194@husc6.UUCP> <1221@crash.CTS.COM>
Organization: National University, San Diego
Lines: 19
Keywords: shared text code libraries UNIX
Summary: Shared Libraries memory positioning
Xref: mnetor comp.sys.amiga:5773 comp.sys.atari.st:4032 comp.sys.m6809:352

In article <1221@crash.CTS.COM>, ford@crash.CTS.COM (Michael Ditto) writes:
> This usually means that when you are creating a new
> shared library you just look at what areas are available and pick one that
> you like, on the (safe) assumption that all libraries could possibly be used
> by one program.  If you for some reason run out of vertual address space, you
> can really stop and figure out which libraries will never both be needed by the
> same program, and make them share addresses.  This is, however, crufty and not
> easily automated (I hate to think about trying to build a Makefile that would
> do this to install a program).


Don't just pick an area of memory at random,  The programmers guide contains
a list of memory areas and what type of function libraries should be
located in each.

If you go through the list you will find that the list is quite extensive.
A small degree of care will prevent any overlapping problems.

Robert.