Hi Karuna,
90Kb is a size that should not trigger any out-of-memory exception;
could you share the XML with us? Maybe it references a schema that
contains large maxOccurs values....
Alberto
At 11.29 24/05/2007 -0400, Kosaraju Karuna-C9013Z wrote:
Hi all,
We are using xerces-c v 2.6 to load XML file using DOM during our
application initialization.
Our input XML is of size 90 KB.
On target Network Element, our application always segfaults during the
initialization and we figured out that the crash is exactly at the API
parseURI(). We are already handling the DOMException, SAXException and
XMLExceptions. But in this case, none of the exceptions are being
caught. When we reduced the size of input XML to 19 KB, the segfault was
not observed. Were there any memory constraints with parseURI() ??
Note that this behavior is observed only on 1 specific NE. The same code
works on different NE's. How will parseURI behaves if sufficient memory
is not available to load the XML? Any pointers on how to approach this
problem will be appreciated.
Thanks,
Karuna
