On Tue, Dec 13, 2016 at 11:15:26PM +0000, Gianfranco Costamagna wrote: > > http://paste.debian.net/902086/ > > ^^ this is the file you requested > > G.
That's great. As I had hoped, ignoring that exception allows SAXCount to complete successfully, and with the expected output (despite the possible memory leak and/or corruption that is still an issue). It now appears to be failing later in the test process. This time there's no exception terminating the program, rather, it's just not printing what it's supposed to be printing. Although, SAXCount should have caught and handled the exception we saw there, but somehow it skipped the handler and terminated the program rather than being caught and handled. So while I'm not sure it will help, there might be benefit to try to get a stack trace from DOMCount. It's possible there's an exception being thrown but it's getting caught/squashed. If someone wants to try to get a stack trace, the command will be libtool --mode=execute gdb --args samples/DOMCount samples/data/personal.xml and the steps inside of gdb will be the same as before. In the mean time, I'll dig back into the source. Thanks! Bill
