Hi Richard,
I can't see how you can get a segfault on the line you indicate, so I guess
the node is somehow corrupted and the segfault is somewhere in the copyOp.
I can only guess at what might be going wrong there, but my first guess
would be the DEEP_COPY_USERDATA.
Laurens.
On Thu, Jan 17, 2019
Hi Lawrence;
Thanks for the help.
Sorry for the confusion; it doesn't actually fail on that line; it fails
deep inside CopyOp; this is the stack trace from the previous code;
osg130-osg.dll!osg::CopyOp::operator()(const osg::Node * node) Line
56 C++
I am out of suggestions, but here are a few questions that I can come up
with:
- did the problematic node come out of the cache, or did it come fresh from
disk?
(modelResult._status has this info)
- Is the parent group (and it's _children vector) still sane?
- If the parent node is still sane,
On 17/01/2019 14:39, Voerman, L. wrote:
I am out of suggestions, but here are a few questions that I can come
up with:
Thanks; much appreciated.
- did the problematic node come out of the cache, or did it come fresh
from disk?
(modelResult._status has this info)
modelResult
4 matches
Mail list logo