From 176c666f36afee12f5cbd1f9615cf21d781fdbde Mon Sep 17 00:00:00 2001
From: Eelco Dolstra <eelco.dolstra@logicblox.com>
Date: Sat, 5 Oct 2013 21:29:48 +0000
Subject: [PATCH] Don't show calls to primops in stack traces

Since they don't have location information, they just give you crap
like:

  while evaluating the builtin function `getAttr':
  while evaluating the builtin function `derivationStrict':
  ...
---
 src/libexpr/eval.cc | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/src/libexpr/eval.cc b/src/libexpr/eval.cc
index 050991a1b..f128b6ad3 100644
--- a/src/libexpr/eval.cc
+++ b/src/libexpr/eval.cc
@@ -728,12 +728,7 @@ void EvalState::callFunction(Value & fun, Value & arg, Value & v)
             /* And call the primop. */
             nrPrimOpCalls++;
             if (countCalls) primOpCalls[primOp->primOp->name]++;
-            try {
-                primOp->primOp->fun(*this, vArgs, v);
-            } catch (Error & e) {
-                addErrorPrefix(e, "while evaluating the builtin function `%1%':\n", primOp->primOp->name);
-                throw;
-            }
+            primOp->primOp->fun(*this, vArgs, v);
         } else {
             v.type = tPrimOpApp;
             v.primOpApp.left = allocValue();