Adjust debugging code in the implementation of the DUP_TOPX bytecode, use

Py_FatalError() instead, and clarify the message somewhat. As discussed on
python-dev.
This commit is contained in:
Thomas Wouters 2000-10-11 23:20:09 +00:00
parent f27f5ab31f
commit 8fb62a2e9a
1 changed files with 1 additions and 5 deletions

View File

@ -775,11 +775,7 @@ eval_code2(PyCodeObject *co, PyObject *globals, PyObject *locals,
PUSH(x);
continue;
default:
fprintf(stderr, "Invalid argument to DUP_TOPX: %d!\n", oparg);
PyErr_SetString(PyExc_SystemError,
"invalid argument to DUP_TOPX");
x = NULL;
break;
Py_FatalError("invalid argument to DUP_TOPX (bytecode corruption?)");
}
break;