[issue24714] Crash with string_at(None)

Changes by STINNER Victor : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue24714] Crash with string_at(None)

STINNER Victor added the comment: ctypes gives you a raw access to the memory. If you try to read unmapped memory areas, the program may or may not crash. Usually, you get a segmentation fault. https://en.wikipedia.org/wiki/Segmentation_fault Python doesn't provide a portable behaviour on segm

[issue24714] Crash with string_at(None)

Changes by Serhiy Storchaka : -- nosy: +amaury.forgeotdarc, belopolsky, meador.inge versions: +Python 3.5, Python 3.6 -Python 3.3 ___ Python tracker ___ _

[issue24714] Crash with string_at(None)

New submission from Michael Toews: On Debian x64 stable with Python 2.7 and 3.4, the following causes a segmentation fault: from ctypes import string_at string_at(None) On Windows 64-bit with Python 2.7 it raises WindowsError and Python 3.3 raises OSError, both showing a message "access viola