From: "Coulter, Scott" <scott.coulter@retek.com>
To: "David Edelsohn" <dje@watson.ibm.com>,
"Joe Buck" <Joe.Buck@synopsys.com>
Cc: <gcc@gcc.gnu.org>
Subject: RE: AIX 5.1 dlopen shared library exception handling problem
Date: Thu, 05 Feb 2004 18:07:00 -0000 [thread overview]
Message-ID: <C736868EB761C04A8909BB038DEABD64095864E2@MSPMAILV1.retek.int> (raw)
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
next reply other threads:[~2004-02-05 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 18:07 Coulter, Scott [this message]
2004-02-05 19:00 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 15:41 Coulter, Scott
2004-02-06 8:38 Joerg.Richter
2004-02-05 15:12 Coulter, Scott
2004-02-05 15:16 ` David Edelsohn
2004-02-05 17:22 ` Joe Buck
2004-02-05 17:25 ` David Edelsohn
2004-02-05 17:34 ` Joe Buck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C736868EB761C04A8909BB038DEABD64095864E2@MSPMAILV1.retek.int \
--to=scott.coulter@retek.com \
--cc=Joe.Buck@synopsys.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).