Re: Performer + Purify + DSO problem

New Message Reply Date view Thread view Subject view Author view

Don Hatch (hatch++at++hell.asd.sgi.com)
Tue, 2 Jul 1996 18:22:58 -0700

On Jul 2, 5:04pm, Ken Sakai wrote:
> Subject: Performer + Purify + DSO problem
>
> Hi,
>
> I am trying to "Purify" my Performer App in an attempt to wring out all the
> little memory-type bugs. Purify on SGI's appears to be having a problem dealing
> with DSO's and keeps erroring out when it tries to deal with the DSO'ed
> database loaders. Linking the "static" versions of the loaders in
> /usr/lib/Performer/Static doesn't help any since the pfdLoadFile stuff
> ALWAYS seems to want to look for a DSO. Is there any way out of this
> problem? Can Purify be made to handle DSO's better? Any tips from
> anyone who has gone down this path would be GREATLY appreciated.

I've had success with Performer 2.0 by making sure
the desired loader DSO is in the first place it tries.
I.e. if purify aborts with the message:
        Purify: Error: match_version can't stat ./libpfobj_ogl.so.2.
then say:
        ln -s /usr/lib/libpfdb/libpfobj_ogl.so .
and it should work the next time. (It purifies the DSO on the fly, I think.)

If you can't get that to work, you can always edit and recompile
your program to calling pfdLoadFile_obj() (or whatever)
explicitly instead of pfdLoadFile().

Don

-- 
Don Hatch  hatch++at++sgi.com  (415) 933-5150  Silicon Graphics, Inc.


=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/   <--new!
            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 2.0b2 on Mon Aug 10 1998 - 17:53:08 PDT

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