[issue26622] test_winreg now logs "Windows exception: code 0x06ba" on Python 3.6

2016-03-23 Thread Roundup Robot
Roundup Robot added the comment: New changeset efcc48cd5bfb by Victor Stinner in branch 'default': faulthandler: only log fatal exceptions https://hg.python.org/cpython/rev/efcc48cd5bfb -- nosy: +python-dev ___ Python tracker

[issue26622] test_winreg now logs "Windows exception: code 0x06ba" on Python 3.6

2016-03-23 Thread STINNER Victor
STINNER Victor added the comment: Ok, I added a check on the EXCEPTION_NONCONTINUABLE flag. test_winreg doesn't log exceptions anymore, but test_faulthandler still pass. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue26622] test_winreg now logs "Windows exception: code 0x06ba" on Python 3.6

2016-03-23 Thread STINNER Victor
STINNER Victor added the comment: Ah, it looks like an exception contains flag, especially the EXCEPTION_NONCONTINUABLE flag. Maybe we can use this one to decide if we must log or not the exception? By the way, is it better to log the exception code as hexadecimal (0x06ba) or decimal (1722)?

[issue26622] test_winreg now logs "Windows exception: code 0x06ba" on Python 3.6

2016-03-23 Thread STINNER Victor
New submission from STINNER Victor: The issue #23848 (change b114dbbe2d31) enhanced the faulthandler module to log Windows exceptions with the Python traceback. It uses AddVectoredExceptionHandler(1, callback) to register the callback. Problem: test_winreg now logs a lot of "Windows exception: