|
From: Ashley P. <api...@co...> - 2008-08-27 21:17:59
|
On Tue, 2008-08-26 at 14:05 -0700, Dave Nomura wrote: > Is there a *.xsd or *.dtd that describes the XML that is output by the > --xml option? > > Are there any consumers of valgrind's xml in the valgrind source tree? I create a utility for converting back from xml output to what the native output would have been normally. I was then able to extend this to work in parallel, effectively merging multiple processes into a single error file showing the sum of the errors. At the time I had this working well enough so that you could hook it into the valgrind test suite and run the tests in XML mode, use my tool to convert it to text and check the results normally. I think there were about three tests failing this way and they were due to mal-formed XML rather than my conversion program. It's still being run as part of the nightly tests by my now ex employer. The tool is open-source however and I'd like to get it into shape and contributed however have lacked the time to do so. > Is there any documentation or suggestions for developing an XML consumer > of valgrind --xml ? I used perl, the XML::Simple module "just works" for me and allows me to get on with the interesting part of the code, the problem with this however is on large input files it can get quite slow. I got most of the way to doing it nativity in XML::Parser however this has sat idle for months now. The speed increase was from a small number of minutes to a small number of seconds for 1MB xml files. Ashley Pittman. |