From: Dorosky, Christopher G (christopher.g.dorosky++at++lmco.com)
Date: 01/22/2001 07:59:22
I saw the same problems. I think it stems from purify not understanding
shared memory. I turned all those warnings off, and was able to run, but
right now purify is a useless tool for memory leaks in performer apps
because of the above problem.
Christopher Dorosky
Lead Electronic Systems Engineer - Real Time Simulation
Lockheed Martin Missiles and Fire Control - Dallas
christopher.g.dorosky++at++lmco.com
972-603-2349
-----Original Message-----
From: yoram [mailto:yoram++at++dreamteam-ltd.com]
Sent: Monday, January 22, 2001 9:22 AM
To: performer list
Subject: Performer purify tests
pfHi,
I have tried running memory tests with Purify on our performer
application.
Even running a simple application with very little data causes purify to
complain about thousands of memory problems - specially around pfWindow
and pfProcess.
Even running tests on the example in /usr/share/Performer.../simple
causes an enourmous amount of problems.
Are these things known?
Is Performer very unclean ( in Purify standards ) ?
Could it be that it is all our fault of bad usage ?
If so, does 'simple' abuse Performer as well ?
regards and thanx
:o)
Yoram Shahak
Dreamteam-ltd.
-----------------------------------------------------------------------
List Archives, FAQ, FTP: 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
This archive was generated by hypermail 2b29 : Mon Jan 22 2001 - 07:59:26 PST