Hi Paul,
The 1.12 release hasn't made any changes relating to getChildNodes.
Other than a handful of small bugfixes, and the switchover to using C++
standard features unconditionally, there aren't any real changes to the
code. But it's certainly possible that some latent bug might have been
exposed. If you could possibly investigate the failure in a bit more
detail, we might be able to pinpoint the fault.
If you compile xalan and your application with "-g3" on Linux, could you
run your program with gdb and "catch throw", and get a backtrace at the
point where the exception is thrown? That will at least tell use where
the failure happens, and if you dig around the stack frames leading up
to the point where it throws, maybe something will be obviously wrong,
like a null pointer or corrupted pointer or something.
Kind regards,
Roger
On 09/08/2020 16:33, Paul Kinnucan wrote:
Hi,
XalanNode.getChildNodes() triggers an error in Xalan 1.12 on Windows
and Linux. All the other node navigation methods work fine, e.g.,
XalanNode *pDoc =
static_cast<XalanNode*>(_LiaisonPtr->parseXMLStream(inputSource));
const XalanNode *pChild = pDoc->getFirstChild(); // works
constXalanNodeList*pList = pDoc->getChildNodes(); // Never returns.
Triggers a std::exception of unknown cause.
I am able to simulate getChildNodes, using getFirstChild and
getNextSibling.
Any idea what the problem is?
Paul
