AIX 5.1 dlopen shared library exception handling problem

[Coulter, Scott]

Does it make sense that this behavior would show up only when loading the library
with dlopen() and not when linking to the library directly?
 
I've already built a test version of our app with only a minimal number of our classes,
trying to see whether this is another instance of the known problem with duplicate symbols.
I haven't yet identified any duplicates.  I'm now working on writing an even smaller
test without any of our app's framework in place.
 
--sdc
scott.coulter@retek.com
 

	-----Original Message----- 
	From: David Edelsohn [mailto:dje@watson.ibm.com] 
	Sent: Thu 2/5/2004 12:25 PM 
	To: Joe Buck 
	Cc: Coulter, Scott; gcc@gcc.gnu.org 
	Subject: Re: AIX 5.1 dlopen shared library exception handling problem 
	
	

	>>>>> Joe Buck writes:
	
	>> Please see existing Bugzilla bug report 13391.
	
	Joe> It doesn't look the same.  You say in that bug report that the issue is
	Joe> that collect2 becomes confused by duplicate symbols.  But in this case,
	Joe> dlopen() is being used to open the shared library, and collect2 is not
	Joe> involved.
	
	        Collect2 generated the shared library.
	
	        According to an analysis in a related bug report, it appears that
	GCC's assumption about the sorting of FDEs is getting confused by the
	address ranges of shared libraries used by AIX.  The duplicate symbols
	cause FDEs for the same symbol to appear in multiple shared libraries.
	
	David