David Florek (dflorek++at++nvl.army.mil)
Fri, 14 Mar 97 13:02:48 EST
I also have submitted a report regarding pfApplyFog() generating the
following apparent bug (message approximated):
PF Warning/Internal: _pfDirtCheck: attempt to reallocate 0 bytes
from/for a NULL pointer
with about the same level of response. About all I've heard is that this
sporadically shows up as a result of various apply() calls (i.e., in C++
internally, fog->apply()). It would seem to me that any attempt to
reallocate 0 bytes for a NULL pointer is indeed a bug and should be
handled before any call to pfRealloc or whatever _pfDirtCheck() is calling.
I suspect that the system is attempting to copy the structure internally,
and isn't correctly checking for NULL pointers, but since Performer has
been so kind as to encapsulate its structure definitions, I can't do much
in the way of tracking the actual cause of the bug.
Does anyone on the Performer team wish to address the recurring
_pfDirtCheck() issues?
Dave
-----------------------------------------------------------------------------
David W. Florek E-OIR Measurements, Inc. Phone: 703 / 704 - 1767
Senior Engineer NVESD Night Vision Lab Email: dflorek++at++nvl.army.mil
Computer Graphics Ft. Belvoir, VA 22060
-----------------------------------------------------------------------------
=======================================================================
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:54 PDT