Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request From: vicorp!dale@uunet.uu.net (Dale Nielsen) Newsgroups: comp.sys.sun Subject: Shared Library Questions Keywords: Miscellaneous Message-ID: <473@brchh104.bnr.ca> Date: 27 Nov 90 20:32:29 GMT Sender: news@brchh104.bnr.ca Organization: Sun-Spots Lines: 29 Approved: Sun-Spots@rice.edu X-Original-Date: Fri, 16 Nov 90 19:20:31 GMT X-Sun-Spots-Digest: Volume 9, Issue 380, message 5 X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu I want to create a shared library on SunOS 4.0, but I have some nagging questions about them that I was unable to find specific answers to in the documentation. Are there tools for testing sharablility? Since a sun shared library will continue to work correctly (although inefficiently) if any of its pages are rendered unsharable, how does one know that this is happening? Is there someway to trace the execution of a program to determine if it is causing any of the shared libraries it uses to have its pages written to, rendering it unsharable. Do local statics need to be in .sa file? There is no discussion of the treatment of initialized statics in the documentation I've found. Since they are local to a module do they count as the "exported globals" referred to by the manual? If a process changes the contents of one of these statics will it cause pieces of the shared library to be unsharable? Do functions whose pointer value is used need special treatment? It seems as though functions whose pointer values are used in comparisons and assignments to function tables as well as being called need to be defined in the .sa library. Is it reasonable to have these definitions be stubs which call the real routine from the shared library? Please respond by email. I will summarize if there is interest. --Dale Nielsen ARPA: dale@vicorp.com V. I. Corporation UUCP: uunet!vicorp!dale 47 Pleasant Street PHONE: (413) 586-4144 x255 Northampton, Massachusetts 01060 FAX: (413) 586-3805