add SetUnhandledExceptionFilter support to win32 so that crash dump c…

[longhun12346]

add SetUnhandledExceptionFilter support to win32 so that crash dump can work as expected, to fix Koromix/koffi#155

[longhun12346]

@Koromix Hi, please take some time look at this. I need to make my app whole as soon as possiable.Thanks.

[longhun12346]

@Koromix Hi, please take some time look at this. I need to make my app whole as soon as possiable.Thanks.

@Koromix Hi, have you check this ? Is there any bug in this pr ?

[Koromix]

Sorry, I don't have much time to work on this right now. Your patch looks good but will have a performance impact, and I'd prefer to find a way to make the SEH unwinder across the Koffi "assembly wall", if possible, so that it can cross the Koffi stack change and frames and properly go up to the default handler.

In the mean time, I encourage you to include your alternative build of koffi.node in your package, especially if it is for a single platform (Win32). The binary file koffi.node is the only file actually needed to use Koffi. All other file in the NPM package are optional (source code for rebuild, test files, etc.). You can use something like require('./patched_koffi.node').

You don't need to load Koffi through the package Koffi index.js entry point. All the JS code does is make some basic checks and implement deprecated functions.

[longhun12346]

Sorry, I don't have much time to work on this right now. Your patch looks good but will have a performance impact, and I'd prefer to find a way to make the SEH unwinder across the Koffi "assembly wall", if possible, so that it can cross the Koffi stack change and frames and properly go up to the default handler.

In the mean time, I encourage you to include your alternative build of koffi.node in your package, especially if it is for a single platform (Win32). The binary file koffi.node is the only file actually needed to use Koffi. All other file in the NPM package are optional (source code for rebuild, test files, etc.). You can use something like require('./patched_koffi.node').

You don't need to load Koffi through the package Koffi index.js entry point. All the JS code does is make some basic checks and implement deprecated functions.

@Koromix Hi, thanks for reply. I know waht you mean, but i think it's not possible to across the Koffi "assembly wall", when dispatch exception windows check the every SEH link list node’s address is between stackbase and stacklimit or not , if we link the exceptionlist back to default stack, the check will fail and windows didn't dispatch exception to our handler(try...catch block). The only way i can find for now is modify stackbase and stacklimit to include both the default stack and koffi's stack area, but since windows may have used them anywhere so it's too dangerous. Or do you have a way to cheat windows on this?