Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
b62efad9
Commit
b62efad9
authored
Jul 25, 2006
by
Armin Rigo
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document the crashers that will not go away soon as "won't fix",
and explain why.
parent
5a9a2a3f
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
15 additions
and
0 deletions
+15
-0
Lib/test/crashers/bogus_code_obj.py
Lib/test/crashers/bogus_code_obj.py
+10
-0
Lib/test/crashers/recursive_call.py
Lib/test/crashers/recursive_call.py
+5
-0
No files found.
Lib/test/crashers/bogus_code_obj.py
View file @
b62efad9
"""
"""
Broken bytecode objects can easily crash the interpreter.
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
import
types
...
...
Lib/test/crashers/recursive_call.py
View file @
b62efad9
#!/usr/bin/env python
#!/usr/bin/env python
# No bug report AFAIK, mail on python-dev on 2006-01-10
# No bug report AFAIK, mail on python-dev on 2006-01-10
# This is a "won't fix" case. It is known that setting a high enough
# recursion limit crashes by overflowing the stack. Unless this is
# redesigned somehow, it won't go away.
import
sys
import
sys
sys
.
setrecursionlimit
(
1
<<
30
)
sys
.
setrecursionlimit
(
1
<<
30
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment