node/test/fixtures/catch-stdout-error.js

function write() {
  try {
    process.stdout.write('Hello, world\n');
  } catch (ex) {
    throw new Error('this should never happen');
  }
  setImmediate(function() {
    write();
  });
}

process.stdout.on('error', function(er) {
  console.error(JSON.stringify(er));
  process.exit(42);
});

write();
Fix #2507 Raise errors less agressively when destroying stdio streams Also, if an error is already provided, then raise the provided error, rather than throwing it with a less helpful 'stdout cannot be closed' message. This is important for properly handling EPIPEs. 2012-01-27 09:14:16 +08:00			`function write() {`
			`try {`
			`process.stdout.write('Hello, world\n');`
			`} catch (ex) {`
			`throw new Error('this should never happen');`
			`}`
test: Use setImmediate for recursive deferral This should have been with 21c741f, but didn't catch it then. Taking our own advice. 2012-11-01 08:07:58 +08:00			`setImmediate(function() {`
Fix #2507 Raise errors less agressively when destroying stdio streams Also, if an error is already provided, then raise the provided error, rather than throwing it with a less helpful 'stdout cannot be closed' message. This is important for properly handling EPIPEs. 2012-01-27 09:14:16 +08:00			`write();`
			`});`
			`}`

Lint all the JavaScripts. 2012-02-19 07:01:35 +08:00			`process.stdout.on('error', function(er) {`
Fix #2507 Raise errors less agressively when destroying stdio streams Also, if an error is already provided, then raise the provided error, rather than throwing it with a less helpful 'stdout cannot be closed' message. This is important for properly handling EPIPEs. 2012-01-27 09:14:16 +08:00			`console.error(JSON.stringify(er));`
			`process.exit(42);`
			`});`

			`write();`