Sharon Clay (src++at++rose.asd.sgi.com)
Sun, 7 Jul 1996 17:07:01 -0700
This error sounds like you have a separate process that is trying
to create new Performer objects and you have not make a pfBuffer
for that process so it is accessing the application process's buffer
and so _bad_ things can happen.
If you are creating new objecs in a DBASE process, you'll want
to create and select a new pfBuffer in a pfConfigStage() callback:
pfSelectBuffer( pfNewBuffer() );
->
-> It looks like a deep error more than a simple warning
-> After this I have some edge pointer effects, switching a parameter i=
->nstead of
-> another, etc. Usually the Segmentation fault is not very far.
->
-> My question is : How can I efficiently and rapidly find the origin o=
->f my
-> error in my source code ?
-> Usually this error occurs in a black boxed routine, so very difficul=
->t to
-> isolate with a debugger like dbx.
-> Sometimes I succeed in finding the bug origin ( sometimes a bad aloc=
->ated
-> pointer ), but the other times it is very difficult, even after read=
->ind and
-> re-reading my code.
->
-> I need a method, or an indication on what is usually the origin of t=
->his kind
-> of error.
Don Hatch put together a great debugging library for finding malloc
corruption. You can find in the ftp archive:
sgigate.sgi.com:~ftp/pub/Performer/src/misc/dmalloc.tar
src.
--
-----{-----{---++at++ -----{----{---++at++ -----{----{---++at++ -----{----{---++at++
Sharon Rose Clay (Fischler) - Silicon Graphics, Advanced Systems Dev.
src++at++sgi.com (415) 933 - 1002 FAX: (415) 965 - 2658 MS 8U-590
http://www.sgi.com/Technology/Performer/
-----{-----{---++at++ -----{----{---++at++ -----{----{---++at++ -----{----{---++at++
=======================================================================
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
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:09 PDT