Commit 2fcb5754 authored by Christophe Rhodes's avatar Christophe Rhodes
Browse files

don't print out "locals" from the global environment

This is important because e.g. the repl evaluation happens in the
global environment, so errors on code called from the repl will pull
up a backtrace with that evaluation frame, which can be inspected for
locals.  But printing out all the locals is a hugely expensive and not
helpful thing to do.
parent 3ca13eb5
...@@ -423,6 +423,9 @@ computeRestartsForEmacs <- function (sldbState) { ...@@ -423,6 +423,9 @@ computeRestartsForEmacs <- function (sldbState) {
`swank:frame-locals-and-catch-tags` <- function(slimeConnection, sldbState, index) { `swank:frame-locals-and-catch-tags` <- function(slimeConnection, sldbState, index) {
frame <- sldbState$frames[[1+index]] frame <- sldbState$frames[[1+index]]
objs <- ls(envir=frame) objs <- ls(envir=frame)
if(identical(frame, globalenv())) {
objs <- c()
}
list(lapply(objs, function(name) { list(quote(`:name`), name, list(lapply(objs, function(name) { list(quote(`:name`), name,
quote(`:id`), 0, quote(`:id`), 0,
quote(`:value`), quote(`:value`),
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment