Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pegasus.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!pegasus!eby
From: eby@pegasus.UUCP (Robert P. Eby)
Newsgroups: net.unix-wizards,net.arch
Subject: Re: Shared runtime libraries - SV shared memory?
Message-ID: <2342@pegasus.UUCP>
Date: Wed, 29-May-85 00:42:01 EDT
Article-I.D.: pegasus.2342
Posted: Wed May 29 00:42:01 1985
Date-Received: Fri, 24-May-85 02:14:41 EDT
References: <1178@phoenix.UUCP>
Organization: AT&T Information Systems, Lincroft NJ
Lines: 18
Xref: watmath net.unix-wizards:13279 net.arch:1237

As a followup to Mike's (phoenix!mzal) article, sdb is useable with a
process running with (our version of 3B2) shared libraries.  However, it
will not handle addresses in the shared library in any easy to use
fashion (you have to interpret the hex for yourself).

The implementation we have was developed originally for the 3B5, and
in theory, should be doable on any System V machine configured with
shared memory.  The things to watch out for are;
	- shared memory has to be executable.  This is true by default
	  on the 3B20 & 3B2, but requires a two line kernel mod on the
	  3B5 (not sure about the vax).
	- you have to be sure to attach the shared library at a fixed
	  virtual address, which is usually differant between differant
	  machine types.  This is so that the ``interface routines'' can
	  find it later when needed.

				Bob Eby
				pegasus!eby