Re: Problem with pfMergeBuffer

New Message Reply Date view Thread view Subject view Author view

John Rohlf (jrohlf++at++tubes)
Fri, 19 Jan 96 12:01:26 PST


>
>
> I have been attempting to create a separate DBASE function that creates
> some geometry and adds it to the scene. However I have found that the
> order in which I create the nodes is critical. For example if I create a
> pfGroup and then create a pfGeode and attach the geode to the group the
> pfMergeBuffer in my separate DBASE function works. If however I create
> the pfGeode and then create the pfGroup the pfMergeBuffer crashes at the
> following location.
> dbx) where
> > 0 pfGroup::nb_clean(int)(0x182f2c04, 0x0, 0x18041274, 0x1831f670, 0xfbe0008)
> ["../../../lib/libpf/pfGroup.C":144, 0x5d127344]
> 1 pfBuffer::pf_prepareNewUpdatables(int)(0x182f2c04, 0x1, 0x18041274, 0x1831f670, 0x182f2bb0)
> ["../../../lib/libpf/pfBuffer.C":752, 0x5d182504]
> 2 pfBuffer::merge(0x182f2c04, 0x1, 0x18041274, 0x1831f670, 0x0)
> ["../../../lib/libpf/pfBuffer.C":556, 0x5d181410]
> 3 pfMergeBuffer(0x182f2c04, 0x1, 0x18041274, 0x1831f670, 0x0)
> ["../../../lib/libpf/cBuffer.C":63, 0x5d1b2534]
> 4 pageDBase(0x18265e10, 0x1, 0x18041274, 0x1831f670, 0x1)
> ["../ladbm.c":65, 0x40a610]
> 5 mpDBase()(0x18265e10, 0x1, 0x18041274, 0x1831f670, 0x0)
> ["../../../lib/libpf/pfProcess.C":3093, 0x5d1cda7c]
> 6 pfConfig(0x18265e10, 0x1, 0x18041274, 0x1831f670, 0x0)
> ["../../../lib/libpf/pfProcess.C":1705, 0x5d15a9a0]
> 7 main(0x18265e10, 0x1, 0x18041274, 0x1831f670, 0x1000f360)
> ["../../common/main.c":100, 0x415b98]
>
>
> An initial work around is to create them in the same top down order that
> they will appear in the scene graph, but this is difficult for some of
> the code I want to execute in the DBASE function.
>

        This is a bug whose workaround is as you describe - create
parents before children.


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:52:16 PDT

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