mirror of
https://github.com/nodejs/node.git
synced 2025-05-04 16:26:26 +00:00
7e516aaac0
The m flag has no effect on regular expressions that don't match the start or the end of a line. PR-URL: https://github.com/nodejs/node/pull/38124 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
33 lines
1.1 KiB
JavaScript
33 lines
1.1 KiB
JavaScript
'use strict';
|
|
if (process.argv[2] === 'child') {
|
|
const common = require('../../common');
|
|
// Trying, catching the exception, and finding the bindings at the `Error`'s
|
|
// `binding` property is done intentionally, because we're also testing what
|
|
// happens when the add-on entry point throws. See test.js.
|
|
try {
|
|
require(`./build/${common.buildType}/test_exception`);
|
|
} catch (anException) {
|
|
anException.binding.createExternal();
|
|
}
|
|
|
|
// Collect garbage 10 times. At least one of those should throw the exception
|
|
// and cause the whole process to bail with it, its text printed to stderr and
|
|
// asserted by the parent process to match expectations.
|
|
let gcCount = 10;
|
|
(function gcLoop() {
|
|
global.gc();
|
|
if (--gcCount > 0) {
|
|
setImmediate(() => gcLoop());
|
|
}
|
|
})();
|
|
return;
|
|
}
|
|
|
|
const assert = require('assert');
|
|
const { spawnSync } = require('child_process');
|
|
const child = spawnSync(process.execPath, [
|
|
'--expose-gc', __filename, 'child',
|
|
]);
|
|
assert.strictEqual(child.signal, null);
|
|
assert.match(child.stderr.toString(), /Error during Finalize/);
|