Xref: utzoo comp.unix.programmer:254 comp.unix.questions:26262 comp.unix.internals:680
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!elroy.jpl.nasa.gov!thyme!kaleb
From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley	)
Newsgroups: comp.unix.programmer,comp.unix.questions,comp.unix.internals
Subject: SunOS shared lib problem
Message-ID: <1990Oct16.214422.1976@thyme.jpl.nasa.gov>
Date: 16 Oct 90 21:44:22 GMT
Sender: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley	)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 29

I thought I'd ask this in comp.sys.sun, but we don't seem to have it
for some reason.  Anyway....

We had a strange problem that we ran into here while building X11R4 and 
Motif 1.1 under SunOS 4.1.  I decided that I wanted the shared libraries 
compiled with optimizing, and the static libraries compiled with debugging 
turned on so that I could debug in Motif.  So I hacked on the Makefiles 
to generate the required objects and libraries.

The problem arose while when we tried to dbx our applications; dbx
would start to read the symbol table, then proceed to dump core.  Given
that the problem only manifested itself after I rebuilt the libraries,
I redid the libraries such that both static and dynamic libraries
were optimized, and the problem went away.

Thus, in order to debug, I ended up building three libraries, where the
third static, debug library has a different name, i.e. libXm_d.a.

Can someone who knows, explain why dbx needs both the static and dynamic
libraries to be the "same"?  Does dbx use symbols in the static to
resolve the dynamic?

advaTHANKSnce

-- 
Kaleb Keithley                      Jet Propulsion Labs
kaleb@thyme.jpl.nasa.gov

causing trouble again.