Michael M. Allbright (m-allbright1++at++ti.com)
Mon, 16 Dec 1996 11:18:40 -0800
Thanks for your reply, I think you summed up the difficulties of real-time
Performer debugging quite well.
I don't think Purify will be a viable solution unless or until PureAtria begins
to offer serious solutions for third-party library instrumentation, which as
far as I know, is not currently part of the Purify picture.
You might be interested to know that ParaSoft Corp's Insure++
(http://www.parasoft.com) has an API designed to let the user (or ParaSoft)
instrument third party libraries. This may be the solution that we have been
looking for. We just got their sales pitch last week, and I am hopeful
regarding it's potential. However, As you noted there are hundreds of low
level graphics calls in Performer, so it is likely that more than the top level
Performer functions need to be instrumented. I am not sure how this could be
done without source code for the library though. Even then, with all the low
level and machine specific calls Performer makes, I wonder if it will be
possible.
By the way, is this (real-time Performer debugging) a common thread here, or am
I the only one distressed by the inability to produce large yet truly robust
Performer apps?
Let me know what you think...
--Mike
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:54:10 PDT