[issue23281] Access violation - pyc file

2015-01-20 Thread STINNER Victor
STINNER Victor added the comment: > we assume it was generated by Python and not an external, malicious source. Said differently: you must not trust .py or .pyc downloaded from untrusted sources. Executing arbitary .py or .pyc file allows to execute arbitrary Python code. Instead of writing c

[issue23281] Access violation - pyc file

2015-01-20 Thread Brett Cannon
Brett Cannon added the comment: If it was created by a fuzzer then this isn't a bug as we do no validation of bytecode formatting as we assume it was generated by Python and not an external, malicious source. -- nosy: +brett.cannon resolution: -> not a bug status: open -> closed

[issue23281] Access violation - pyc file

2015-01-20 Thread Paweł Zduniak
Paweł Zduniak added the comment: This file is created by fuzzer -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue23281] Access violation - pyc file

2015-01-20 Thread Eric V. Smith
Eric V. Smith added the comment: Was this file generated by CPython from a .py file? If so, can you share the .py file? If not, how was this file generated? As eryksun says, it appears to not be a valid .pyc file. -- nosy: +eric.smith ___ Python tr

[issue23281] Access violation - pyc file

2015-01-20 Thread eryksun
eryksun added the comment: You attached a corrupt bytecode cache for stdlib bisect.py: >>> f = open('test.pyc', 'rb') >>> magic,tstamp = struct.unpack('>> magic27 = 62211 | (ord('\r') << 16) | (ord('\n') << 24) >>> magic == magic27 True >>> datetime.fromtimestamp(tstamp)

[issue23281] Access violation - pyc file

2015-01-19 Thread Paweł Zduniak
New submission from Paweł Zduniak: (950.e58): Access violation - code c005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. *** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\Sys