Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site phoenix.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!pegasus!phoenix!mzal
From: mzal@phoenix.UUCP (Mike Zaleski)
Newsgroups: net.unix-wizards,net.arch
Subject: Re: Shared runtime libraries - SV shared memory?
Message-ID: <1178@phoenix.UUCP>
Date: Wed, 22-May-85 21:45:00 EDT
Article-I.D.: phoenix.1178
Posted: Wed May 22 21:45:00 1985
Date-Received: Thu, 23-May-85 04:25:01 EDT
Organization: AT&T Information Systems, Lincroft NJ
Lines: 23
Xref: watmath net.unix-wizards:13275 net.arch:1235

>> I understand the new AT&T 7300 micro supports some type of
>> shared libraries.  Again, I'm not sure of all the details,
>> but I have heard that you can't use the debugger with a
>> program using the shared libraries.

I'm not sure about the 7300 micro, but on our 3b2's we run
a shared runtime library with our XXX CLASSIFIED XXX project.
The basic idea is that a set of shareable routines is built
with the loader and loaded by a special process at boot time
(or manually while the system is running if no one is using the
shared runtime library).  The routines are accessed by small
assembler routines which are in a different library which developers
use to link their programs with.

Because I'm not doing development on our project, I'm not sure
about the debugger statement.  What I *think* is the case is that
SDB can be used, but is not very helpful on errors in the shared
runtime library.

We've been using this setup for a while and it works quite nicely.

-- "The Model Citizen" Mike^Z
   Zaleski@Rutgers  [ allegra, ihnp4 ] pegasus!mzal