Project

Profile

Help

Bug #2706

Unlicensed SchemaValidator segmentation error

Added by O'Neil Delpratt almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Category:
C++ API
Start date:
2016-04-11
Due date:
% Done:

100%

Found in version:
1.0.1
Fixed in version:
1.0.2

Description

A user recently discovered that instantiating an unlicensed copy of the SchemaValidator does not terminate properly and will eventually lead to a segmentation error if the SchemaValidator object is later used. This can happen where the license file is not present in EE, a call made via PE or HE.

Details on the error and what is produced see https://github.com/rimmartin/saxon-node/issues/7#issuecomment-206097271

In this situation, we need to properly check if an exception is thrown in the constructor. A user can then check this in their code as it is their responsibility to make sure a license file is available and that they are using the correct product.

History

#1 Updated by O'Neil Delpratt almost 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Bug fixed in the constructor of the SchemaValidator class.

#2 Updated by O'Neil Delpratt almost 2 years ago

  • Subject changed from Unlicensed SchemaValidator segmentation erro to Unlicensed SchemaValidator segmentation error

#3 Updated by O'Neil Delpratt over 1 year ago

  • Fixed in version set to 1.0.2

Bug fix applied in the Saxon/C 1.0.2 maintenance release

#4 Updated by O'Neil Delpratt over 1 year ago

  • Status changed from Resolved to Closed

Please register to edit this issue

Also available in: Atom PDF