kc3-lang/libxml2/python/tests/xpath.py

• Show log

  Commit

• Hash : 4e1b26cf
  Author :
  Date : 2002-02-03T20:13:06
  

  change a small bit in the way valididy error messages get initialized
  
  * parserInternals.c: change a small bit in the way valididy
    error messages get initialized
  * python/TODO python/libxml.c python/libxml2-python-api.xml
    python/libxml2class.txt python/libxml_wrap.h python/types.c:
    added some memory debugging to track leaks at the libxml2 level
  * python/tests/*.py: changed all tests to check for leaks,
    there is just one left in XPath extension registrations.
  daniel
  

Download

• python/tests/xpath.py

• #!/usr/bin/python -u
  #
  # this test exercise the XPath basic engine, parser, etc, and
  # allows to detect memory leaks
  #
  import sys
  import libxml2
  
  # Memory debug specific
  libxml2.debugMemory(1)
  
  doc = libxml2.parseFile("tst.xml")
  if doc.name != "tst.xml":
      print "doc.name error"
      sys.exit(1);
  
  ctxt = doc.xpathNewContext()
  res = ctxt.xpathEval("//*")
  if len(res) != 2:
      print "xpath query: wrong node set size"
      sys.exit(1)
  if res[0].name != "doc" or res[1].name != "foo":
      print "xpath query: wrong node set value"
      sys.exit(1)
  doc.freeDoc()
  i = 1000
  while i > 0:
      doc = libxml2.parseFile("tst.xml")
      ctxt = doc.xpathNewContext()
      res = ctxt.xpathEval("//*")
      doc.freeDoc()
      i = i -1
  del ctxt
  
  # Memory debug specific
  libxml2.cleanupParser()
  if libxml2.debugMemory(1) == 0:
      print "OK"
  else:
      print "Memory leak %d bytes" % (libxml2.debugMemory(1))
      libxml2.dumpMemory()
  

Download