pfFlatten core dumps.

New Message Reply Date view Thread view Subject view Author view

Robert Doyle (doyle++at++overlord.nrl.navy.mil)
Thu, 16 May 1996 16:20:19 -0400

A January '96 posting in the Performer archives refered to a problem with core
dumps arising from bounding-box calculations at the geoset level. I encounter a
similar problem when using pfFlatten to transform some simple geometry below
SCS nodes. Unfortunately, January is the most recently archived month. If a
solution was subsequently posted and someone would repost a copy, I would be
grateful. My stack trace shows:

(dbx) where
> 0 pfGeoSet::pr_computeBBox(void)(0x18096590, 0x10000066, 0x2, 0xc)
["../../../lib/libpr/pfGeoSet.C":2055, 0x5ce0f4f8]
   1 pfGeoSet::setBound(pfBox*,int)(0x18096590, 0x10000066, 0x2, 0xc)
["../../../lib/libpr/pfGeoSet.C":1371, 0x5ce28944]
   2 pfGeode::nb_flatten(pfTraverser*)(0x10030d80, 0x7fffa598, 0x180964b0, 0xc)
["../../../lib/libpf/pfGeode.C":398, 0x5ce553a4]
   3 pfGroup::nb_flatten(pfTraverser*)(0x180dfb60, 0x7fffa598, 0x2, 0xc)
["../../../lib/libpf/pfGroup.C":358, 0x5ce57940]
   4 pfSCS::nb_flatten(pfTraverser*)(0x180dfb60, 0x7fffa598, 0x2, 0xc)
["../../../lib/libpf/pfSCS.C":339, 0x5ce85268]
   5 pfGroup::nb_flatten(pfTraverser*)(0x180dfae0, 0x7fffa598, 0x2, 0xc)
["../../../lib/libpf/pfGroup.C":358, 0x5ce57940]
   6 pfNode::nb_flatten(int)(0x180dfae0, 0x0, 0x2, 0xc)
["../../../lib/libpf/pfNode.C":1271, 0x5ce5ac78]
   7 pfFlatten(0x10030d80, 0x0, 0x2, 0xc) ["../../../lib/libpf/cNode.C":309,
0x5ce91ecc]
   8 main(0x1, 0x18040ca0, 0x2, 0xc) ["../callcull.c":198, 0x403ec8]
   9 __start() ["crt1text.s":133, 0x40385c]

Thanks,
Bob Doyle

-- 
Robert J. Doyle, Jr.            http://overlord.nrl.navy.mil
Code 6110                       e-mail: doyle++at++overlord.nrl.navy.mil
Naval Research Laboratory       fax: 202-404-8119
Washington, DC  20375-5000      phone: 202-404-8513

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:54 PDT

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