To check simply run
ctest -R url-
and look into the build/Testing/Temporary/LastTest.log.
Here is what you will see:
test xqxq/url-schema-resolver
[...]
=== end of result ===
testdriver: success (non-canonical result # 1 matches)
testdriver: test runtime was 37041us
testdriver: success
ID: 78 Referenced URI: http://www.zorba-xquery.com/modules/xqxq/url-resolver
ID: 113 Referenced URI: http://www.zorba-xquery.com/modules/xqxq
terminate called after throwing an instance of 'zorba::ZorbaException'
what(): Zorba did not close properly, objects may still in memory.
2 referenced URI(s) remain in the string pool.
For help avoiding this message please refer to http://www.zorba-xquery.com/html/documentation in section General Architecture -> Memory Leaks.
There is a memory leak in the implementation.
To check simply run Temporary/ LastTest. log.
ctest -R url-
and look into the build/Testing/
Here is what you will see:
test xqxq/url- schema- resolver www.zorba- xquery. com/modules/ xqxq/url- resolver www.zorba- xquery. com/modules/ xqxq :ZorbaException ' www.zorba- xquery. com/html/ documentation in section General Architecture -> Memory Leaks.
[...]
=== end of result ===
testdriver: success (non-canonical result # 1 matches)
testdriver: test runtime was 37041us
testdriver: success
ID: 78 Referenced URI: http://
ID: 113 Referenced URI: http://
terminate called after throwing an instance of 'zorba:
what(): Zorba did not close properly, objects may still in memory.
2 referenced URI(s) remain in the string pool.
For help avoiding this message please refer to http://