[info-performer] Performer - Static libs - Unresolved symbol pfNewLayer

New Message Reply Date view Thread view Subject view Author view

From: Jamulla, John D. (AMHERST) (jdj++at++amherst.com)
Date: 09/24/2002 06:40:38


Hello,

I have another problem with linking our APP with Performer, this time
(which is the ultimate goal for me) when linking our app against
Performer 2.4.2 libs STATICALLY. I am doing this with 7.3.1.3m compilers
on IRIX 6.5.13m. Those who see the same named APP, I just linked this
one with the STATIC libs by changing the -L paths to point to
-L /usr/lib32/Performer/Static and -L
/usr/lib32/Performer/Static/libpfdb. I do use -no_unresolved

The problem I'm aving is that when we run a very specific OpenFlight
file as input to our app, we get an error message and the app won't run.

I used rlddebug with 'trace' turned on, I won't send the entire output,
but here's the relevant part:
------------------------------------------------------------------------
------------------------------
/net/iris41/home/tues/bin/n32/debug/SituationDisplay: [rld] Entering RLD
through lazy_text_resolve
156701: 11:42:32 /net/iris41/home/tues/bin/n32/debug/SituationDisplay:
[rld] lazy text of pfNewLayer in /usr/lib32/libpfdb/libpfflt.so.5, ra ==
0x4e4b828, stub == 0x4e35c40
156701: 11:42:32 /net/iris41/home/tues/bin/n32/debug/SituationDisplay:
rld: Fatal Error exit/longjmp: attempted access to unresolvable symbol
in /usr/lib32/libpfdb/libpfflt.so.5: pfNewLayer
156701:/net/iris41/home/tues/bin/n32/debug/SituationDisplay: rld: Fatal
Error: attempted access to unresolvable symbol in
/usr/lib32/libpfdb/libpfflt.so.5: pfNewLayer
156778: 11:42:35

The app is LAZY DLOPENing the libpfflt.so (which something in performer
is causing)
and this is why our STATIC executable doesn't work in certain cases. I
believe if I understand correctly, the SGI team would be the programmers
who wrote the code to do the lazy DLOPENing. We have no control over
this. This appears to be some sort of "bug".

I was wondering if this is a known problem, maybe it's fixed if I link
against performer 2.5 libs?

Any help would be greatly appreciated.

Sincerely,
        John J.

---
John D. Jamulla - Senior Engineer
Northrop Grumman Corporation
Electronic Systems
Amherst Systems
Buffalo N.Y. 14221, (716) 631-0088
jdj++at++amherst.com, or j.jamulla++at++ieee.org


----------------------------------------------------------------------- List Archives, Info, FAQ: http://www.sgi.com/software/performer/ Open Development Project: http://oss.sgi.com/projects/performer/ Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com -----------------------------------------------------------------------


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Sep 26 2002 - 07:35:10 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.