[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'
New submission from Fynn Be : 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: 303751 nosy: Fynn Be, haypo, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: faulthandler dumps 'Windows fatal exception: code 0xe06d7363' type: behavior versions: Python 3.6 ___ Python tracker <https://bugs.python.org/issue31701> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'
Fynn Be added the comment: Here is a git repository with a test module and a test script: https://github.com/FynnBe/faulthandler-spam -- ___ Python tracker <https://bugs.python.org/issue31701> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'
Fynn Be 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): File "test.py", line 5 in caught test error: c++ error message ``` The 'Windows fatal exception: code 0xe06d7363' is only caused by a c++ exception thrown (regardless if it is handled or not). More on the error code is here: https://support.microsoft.com/de-de/help/185294/prb-exception-code-0xe06d7363-when-calling-win32-seh-apis The last line 'caught test error: c++ error message' is generated within the test module, where the error is caught. In larger projects these tracebacks spam the faulthandler's output, as this is valid code and occurs often (for example for an IndexError raised in a c++ extension to end a for loop). -- ___ Python tracker <https://bugs.python.org/issue31701> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'
Fynn Be 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(0xE06D7363 & 0x8000) == True' > with the initial "E" standing for "exception" and the final 3 bytes > (0x6D7363) representing the ASCII values of "msc" https://support.microsoft.com/de-de/help/185294/prb-exception-code-0xe06d7363-when-calling-win32-seh-apis In this context it seems like a coincidence to me. -- ___ Python tracker <https://bugs.python.org/issue31701> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
