[issue12632] Windows GPF with Code Page 65001

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

First, a call to abort() is not a GPF: it's not an interrupt from the kernel or the OS, it's just an explicit (albeit brutal) way to exit from an application.  There is no potential back door here.

Then, the "Fatal Python error:" line is written to stderr. It's possible to redirect it (try with "python 2>t.txt").
The message "This application..." is written by the Microsoft C Runtime Library, I don't know if it is also printed to stderr.

Furthermore, in this case the application will have a particular exit code, IIRC it's 3; from the cmd.exe you can get it with "echo %ERRORLEVEL%".  Normally python processes exit with a status of 0 (everything is OK) or 1 (if an exception is raised and not caught)

Finally, the "fix" you suggest would be applicable if python used WriteConsole or WriteFile... but it does not!  It uses the write() function, which probably calls WriteConsole or WriteFile at some point, but does not take unicode characters...

----------
nosy: +amaury.forgeotdarc

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12632>
_______________________________________