Unhandled Win32 exception - no AeDebug postmortem or UnhandledExceptionFilter callback #27099

Activity

1. bzoz commented on Apr 11, 2019

   

   bzoz

   on Apr 11, 2019

   Contributor

   More actions

   You can try commenting out those lines and rebuilding Node:

   node/deps/uv/src/win/core.c

   Lines 177 to 194 in 655c90b

   	/* Tell Windows that we will handle critical errors. */
   	SetErrorMode(SEM_FAILCRITICALERRORS | SEM_NOGPFAULTERRORBOX |
   	SEM_NOOPENFILEERRORBOX);
   	/* Tell the CRT to not exit the application when an invalid parameter is
   	* passed. The main issue is that invalid FDs will trigger this behavior.
   	*/
   	#if !defined(__MINGW32__) || __MSVCRT_VERSION__ >= 0x800
   	_set_invalid_parameter_handler(uv__crt_invalid_parameter_handler);
   	#endif
   	/* We also need to setup our debug report handler because some CRT
   	* functions (eg _get_osfhandle) raise an assert when called with invalid
   	* FDs even though they return the proper error code in the release build.
   	*/
   	#if defined(_DEBUG) && (defined(_MSC_VER) || defined(__MINGW64_VERSION_MAJOR))
   	_CrtSetReportHook(uv__crt_dbg_report_handler);
   	#endif

   If you are testing your own modules you should have almost everything you need to build Node already available, maybe missing NASM. Check out our bootstraping guide: https://github.com/nodejs/node/tree/master/tools/bootstrap#windows . The build process itself is as simple as checking out the source code and running vcbuild.bat.
3. ghost closed this as completedon Apr 12, 2019