Re: pfCycleBuffer's causing SEGV's

New Message Reply Date view Thread view Subject view Author view

Sharon Clay (src++at++rose.asd.sgi.com)
Mon, 9 Sep 1996 12:31:12 -0700


+>---- On Sep 9, 3:31pm, Brian Furtaw wrote:
> Subject: pfCycleBuffer's causing SEGV's
->
->Question:
->
->Do pfCycleBuffers work with indexed pfGeoSets?
->
->The reason I ask is this, the man page says this,
-> While pfCycleBuffers can be used for generic dynamic data, a
-> prominent use is as attribute arrays for pfGeoSets. The function
-> pfGeoSet::setAttr accepts pfCycleBuffer memory for attribute
-> arrays and the pfGeoSet will index the appropriate pfCycleMemory
-> when rendering and intersection testing.
->
-> Currently, pfGeoSets do not support pfCycleBuffer index lists.
->
->Does this mean the index list or the whole pfGeoSet containing the

Just the index list.

->index list. I am trying to use a CycleBuffer in an indexed GeoSet as
->the list of vertices and I am getting coredumps (SEGVs). So the
->CycleBuffer's are causing memory to be accessed illegally somewhere,
->without CycleBuffers the code runs fine.

You might try purify if you can dump it in single process (will need to use
NULL for your arena for purify to track the buffers) or else just
try dmalloc to see if at least it detects memory corruption from
writing to the buffers.

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/
            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:31 PDT

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