Is there any sort of memory constraint on the size of a DOMDocument, and it's collective assoicated nodes? I'm getting mysterious segmentation violation inside getLocalName or getNodeType, when the program reaches approximately 80-90 MB of virtual storage usage, most of which is used by xerces (2.2.0 - I can't try 2.3.0 as I also use pathan).
I'm off to do some debugging inside xerces now, but it would help to know if there is a definite limit (O/S is Redhat linux 8.0, and ulimit is unlimited).. -- Colin Paul Adams Preston Lancashire --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]