From 4e6f048ef0f201718ac1a24ff917fb4d42a2b181 Mon Sep 17 00:00:00 2001 From: Nilay Vaish Date: Mon, 10 Sep 2012 12:20:34 -0500 Subject: [PATCH] Ruby Slicc: remove the call to cin.get() function If I understand correctly, this was put in place so that a debugger can be attached when the protocol aborts. While this sounds useful, it is a problem when the simulation is not being actively monitored. I think it is better to remove this. --- src/mem/slicc/ast/AST.py | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/src/mem/slicc/ast/AST.py b/src/mem/slicc/ast/AST.py index b99451019..9e3844445 100644 --- a/src/mem/slicc/ast/AST.py +++ b/src/mem/slicc/ast/AST.py @@ -54,14 +54,7 @@ class AST(PairContainer): message = message % args code = self.slicc.codeFormatter() code(''' -char c; -cerr << "Runtime Error at ${{self.location}}, Ruby Time: " - << g_system_ptr->getTime() << ": " - << $message - << ", PID: " << getpid() << endl - << "press return to continue." << endl; -cin.get(c); -abort(); +panic("Runtime Error at ${{self.location}}, Ruby Time: %d, %s.\\n", + g_system_ptr->getTime(), $message); ''') - return code -- 2.30.2