doc: remove old system_errors · nodejs/node@a5314a1 (original) (raw)
`@@ -355,9 +355,6 @@ The number of frames captured by the stack trace is bounded by the smaller of
`
355
355
`` Error.stackTraceLimit
or the number of available frames on the current event
``
356
356
`loop tick.
`
357
357
``
358
``
`` -
System-level errors are generated as augmented Error
instances, which are
``
359
``
`-
detailed here.
`
360
``
-
361
358
`## Class: AssertionError
`
362
359
``
363
360
`` A subclass of Error
that indicates the failure of an assertion. For details,
``
`@@ -442,20 +439,13 @@ Some exceptions are unrecoverable at the JavaScript layer. Such exceptions
`
442
439
`` will always cause the Node.js process to crash. Examples include assert()
``
443
440
`` checks or abort()
calls in the C++ layer.
``
444
441
``
445
``
`-
System Errors
`
``
442
`+
Class: SystemError
`
446
443
``
447
444
`Node.js generates system errors when exceptions occur within its runtime
`
448
445
`environment. These usually occur when an application violates an operating
`
449
446
`system constraint. For example, a system error will occur if an application
`
450
447
`attempts to read a file that does not exist.
`
451
448
``
452
``
`-
System errors are usually generated at the syscall level. For a comprehensive
`
453
``
`` -
list, see the [errno
(3) man page][].
``
454
``
-
455
``
`` -
In Node.js, system errors are Error
objects with extra properties.
``
456
``
-
457
``
`-
Class: SystemError
`
458
``
-
459
449
`` * address
{string} If present, the address to which a network connection
``
460
450
` failed
`
461
451
`` * code
{string} The string error code
``
`` @@ -468,27 +458,27 @@ In Node.js, system errors are Error
objects with extra properties.
``
468
458
`` * port
{number} If present, the network connection port that is not available
``
469
459
`` * syscall
{string} The name of the system call that triggered the error
``
470
460
``
471
``
`-
error.address
`
``
461
`+
error.address
`
472
462
``
473
463
`* {string}
`
474
464
``
475
465
`` If present, error.address
is a string describing the address to which a
``
476
466
`network connection failed.
`
477
467
``
478
``
`-
error.code
`
``
468
`+
error.code
`
479
469
``
480
470
`* {string}
`
481
471
``
482
472
`` The error.code
property is a string representing the error code.
``
483
473
``
484
``
`-
error.dest
`
``
474
`+
error.dest
`
485
475
``
486
476
`* {string}
`
487
477
``
488
478
`` If present, error.dest
is the file path destination when reporting a file
``
489
479
`system error.
`
490
480
``
491
``
`-
error.errno
`
``
481
`+
error.errno
`
492
482
``
493
483
`* {string|number}
`
494
484
``
`@@ -498,31 +488,31 @@ negative value which corresponds to the error code defined in
`
498
488
`` (deps/uv/include/uv/errno.h
in the Node.js source tree) for details. In case
``
499
489
`` of a string, it is the same as error.code
.
``
500
490
``
501
``
`-
error.info
`
``
491
`+
error.info
`
502
492
``
503
493
`* {Object}
`
504
494
``
505
495
`` If present, error.info
is an object with details about the error condition.
``
506
496
``
507
``
`-
error.message
`
``
497
`+
error.message
`
508
498
``
509
499
`* {string}
`
510
500
``
511
501
`` error.message
is a system-provided human-readable description of the error.
``
512
502
``
513
``
`-
error.path
`
``
503
`+
error.path
`
514
504
``
515
505
`* {string}
`
516
506
``
517
507
`` If present, error.path
is a string containing a relevant invalid pathname.
``
518
508
``
519
``
`-
error.port
`
``
509
`+
error.port
`
520
510
``
521
511
`* {number}
`
522
512
``
523
513
`` If present, error.port
is the network connection port that is not available.
``
524
514
``
525
``
`-
error.syscall
`
``
515
`+
error.syscall
`
526
516
``
527
517
`* {string}
`
528
518
``