In 2.7 we added more descriptive callstacks when javascript exceptions propagate up to the top javascript level. This helped with debugging javascript scripts run by the shell, such as jstests run by the testing framework.

Unfortunately, interactive shell use also now generates these backtraces, even though they are of little use to interactive users. We should specifically suppress these callstacks in the shell's read-eval-print-loop.