[issue10509] PyTokenizer_FindEncoding can lead to a segfault if bad characters are found

Andreas Stührk added the comment: Yes, it is (at the latest since msg124018). -- resolution: -> duplicate status: open -> closed ___ Python tracker ___

[issue10509] PyTokenizer_FindEncoding can lead to a segfault if bad characters are found

Ron Adam added the comment: Is this a duplicate of issue 9319? -- nosy: +ron_adam ___ Python tracker ___ ___ Python-bugs-list mailing

[issue10509] PyTokenizer_FindEncoding can lead to a segfault if bad characters are found

Changes by Ezio Melotti : -- nosy: +ezio.melotti stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue10509] PyTokenizer_FindEncoding can lead to a segfault if bad characters are found

Changes by Andreas Stührk : -- keywords: +patch Added file: http://bugs.python.org/file19775/PyTokenizer_FindEncoding_fix.patch ___ Python tracker ___ ___

[issue10509] PyTokenizer_FindEncoding can lead to a segfault if bad characters are found

New submission from Andreas Stührk : If a non-ascii character is found and there isn't an encoding cookie, a SyntaxError is raised (in `decoding_fgets`) that includes the path of the file (using ``tok->filename``), but that path is never set. You can easily reproduce the crash by calling `imp.