diff options
| author | cinap_lenrek <cinap_lenrek@localhost> | 2011-05-04 05:41:33 +0000 |
|---|---|---|
| committer | cinap_lenrek <cinap_lenrek@localhost> | 2011-05-04 05:41:33 +0000 |
| commit | b8436b026a90291ba26afa4f7a2700720b03339f (patch) | |
| tree | 3098aede87640c80567ecb31022e0404a8b5ec75 /sys/lib/python/test/crashers/bogus_code_obj.py | |
| parent | 6c1b42188259a6f1636cd15a9570b18af03e2dbb (diff) | |
remove python test cases
Diffstat (limited to 'sys/lib/python/test/crashers/bogus_code_obj.py')
| -rw-r--r-- | sys/lib/python/test/crashers/bogus_code_obj.py | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/sys/lib/python/test/crashers/bogus_code_obj.py b/sys/lib/python/test/crashers/bogus_code_obj.py deleted file mode 100644 index 613ae518d..000000000 --- a/sys/lib/python/test/crashers/bogus_code_obj.py +++ /dev/null @@ -1,19 +0,0 @@ -""" -Broken bytecode objects can easily crash the interpreter. - -This is not going to be fixed. It is generally agreed that there is no -point in writing a bytecode verifier and putting it in CPython just for -this. Moreover, a verifier is bound to accept only a subset of all safe -bytecodes, so it could lead to unnecessary breakage. - -For security purposes, "restricted" interpreters are not going to let -the user build or load random bytecodes anyway. Otherwise, this is a -"won't fix" case. - -""" - -import types - -co = types.CodeType(0, 0, 0, 0, '\x04\x71\x00\x00', (), - (), (), '', '', 1, '') -exec co |