This enables the option `--force-node-api-uncaught-exceptions-policy` for a specific Node-API addon when it is compiled with `NAPI_EXPERIMENTAL` (and this would be the default behavior when `NAPI_VERSION` 10 releases). This would not break existing Node-API addons. PR-URL: https://github.com/nodejs/node/pull/49313 Refs: https://github.com/nodejs/node/pull/36510 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Gabriel Schulhof <gabrielschulhof@gmail.com>
32 lines
814 B
JavaScript
32 lines
814 B
JavaScript
'use strict';
|
|
|
|
const common = require('../../common');
|
|
const assert = require('assert');
|
|
|
|
function testUncaughtException(binding) {
|
|
const callbackCheck = common.mustCall((err) => {
|
|
assert.throws(() => { throw err; }, /callback error/);
|
|
process.removeListener('uncaughtException', callbackCheck);
|
|
process.on('uncaughtException', finalizerCheck);
|
|
});
|
|
const finalizerCheck = common.mustCall((err) => {
|
|
assert.throws(() => { throw err; }, /finalizer error/);
|
|
});
|
|
process.on('uncaughtException', callbackCheck);
|
|
|
|
binding.CallIntoModule(
|
|
common.mustCall(() => {
|
|
throw new Error('callback error');
|
|
}),
|
|
{},
|
|
'resource_name',
|
|
common.mustCall(function finalizer() {
|
|
throw new Error('finalizer error');
|
|
}),
|
|
);
|
|
}
|
|
|
|
module.exports = {
|
|
testUncaughtException,
|
|
};
|