| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Co-authored-by: Michaël Zasso <targos@protonmail.com>
Co-authored-by: Michaël Zasso <targos@protonmail.com>
Sorry, something went wrong.
|
CI is green except a timeout |
Sorry, something went wrong.
PR-URL: #38174 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Landed in 837f7e2f71ce |
Sorry, something went wrong.
PR-URL: #38174 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Sorry for missing the ping: just FYI SetIsolateErrorHandlers() can install error handlers that print uncaught exceptions and it's used by the ordinary Node.js instances - I don't quite remember why it wasn't used by mksnapshot, though. Also there are some routines in node_errors.cc that can be reused to print these errors. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This came up while trying to debug some stuff going on in the snapshot, makes debugging a lot easier. IDK if we want to do something other than use abort() here.