[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

2017-10-05 Thread Fynn Be
Fynn Be <thefyn...@gmail.com> added the comment: > Are you asking to *ignore* all 0xE06D7363 exceptions? Yes. This error is only indicating that an error was thrown, regardless if it was handled or not. Therefore it should not be treated as fatal, but it is by faulthandler: 'bool(0

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

2017-10-05 Thread Fynn Be
Fynn Be <thefyn...@gmail.com> added the comment: In the github repository there is 'build.bat' that creates the mscv 14 solution, builds it and runs the 'test.py'. Here is the output: ``` Windows fatal exception: code 0xe06d7363 Current thread 0x462c (most recent call first):

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

2017-10-05 Thread Fynn Be
Fynn Be <thefyn...@gmail.com> added the comment: Here is a git repository with a test module and a test script: https://github.com/FynnBe/faulthandler-spam -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

2017-10-05 Thread Fynn Be
New submission from Fynn Be <thefyn...@gmail.com>: c++ extension compiled with MSVC 14 using python 3.6.2 on Windows 10 x64 Whenever a C++ exception is thrown in an extension the faulthandler dumps a traceback to it, even if it is caught. -- components: Windows messages: 30375