38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync# this test exercise the XPath basic engine, parser, etc, and
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync# allows to detect memory leaks
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync# Memory debug specific
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync print "doc.name error"
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync print "xpath query: wrong node set size"
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync print "xpath query: wrong node set value"
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync print "xpath query: wrong node set size"
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync print "xpath query: wrong node set value"
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsyncwhile i > 0:
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync# Memory debug specific
38ae7e4efe803ea78b6499cd05a394db32623e41vboxsync print "Memory leak %d bytes" % (libxml2.debugMemory(1))