[issue47137] MemoryError in codeop.compile_command

Change by Eric V. Smith : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue47137] MemoryError in codeop.compile_command

Pablo Galindo Salgado added the comment: > I suspect backporting the fix to older versions won't be possible. Yeah, very much the case unfortunately -- ___ Python tracker

[issue47137] MemoryError in codeop.compile_command

Change by Eric V. Smith : -- nosy: +pablogsal title: MemoryError -> MemoryError in codeop.compile_command versions: +Python 3.8 ___ Python tracker ___

[issue47137] MemoryError

qiu <1425166...@qq.com> added the comment: y
-- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47137] MemoryError

Eric V. Smith added the comment: A simpler reproducer is: codeop.compile_command('[' * 100) Verified I get MemoryError on cygwin PYthon 3.8.12. A length of 99 does not show a problem. On Windows 3.11.0a5+, I get: >>> codeop.compile_command('[' * 201) Traceback (most recent call last):

[issue47137] MemoryError

qiu <1425166...@qq.com> added the comment: hello,Did you get the E-mail about one random input I sent you? one random input is

[issue47137] MemoryError

qiu <1425166...@qq.com> added the comment: 9 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47137] MemoryError

Jacob Nilsson added the comment: Python 3.6 reach end of life in December 2021, is this error reproducible in Python 3.7 and above? If that is still the case, do you have an example of an exact input causing this crash? "random input" is not a lot to go by. -- nosy: +ajoino

[issue47137] MemoryError

New submission from qiu <1425166...@qq.com>: Traceback (most recent call last): File "python_AFL.py", line 110, in runFuzzer runtime = runApplication(input_path, mode) File "python_AFL.py", line 75, in runApplication exec(f.read(), {'buff': input_data}) File "", line 16, in