From 8fb62a2e9a9c61c41560d5edb318ac1070dadb16 Mon Sep 17 00:00:00 2001 From: Thomas Wouters Date: Wed, 11 Oct 2000 23:20:09 +0000 Subject: 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. --- Python/ceval.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/Python/ceval.c b/Python/ceval.c index ca38c68..ce4b67a 100644 --- a/Python/ceval.c +++ b/Python/ceval.c @@ -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; -- cgit v0.12