You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
diff --git a/R/xts.methods.R b/R/xts.methods.R
index c94ac6b..5299061 100644
--- a/R/xts.methods.R+++ b/R/xts.methods.R@@ -282,8 +282,9 @@ window_idx <- function(x, index. = NULL, start = NULL, end = NULL)
# Translate from user .index to xts index
# We get back upper bound of index as per findInterval
tmp <- base_idx[firstlast]
-+gctorture(TRUE)
res <- .Call("fill_window_dups_rev", tmp, .index(x), PACKAGE = "xts")
+gctorture(FALSE)
firstlast <- rev(res)
}
Description
I've been seeing intermitted segfaults in my R code recently. One gave the following output:
Expected behavior
No segfault!
Minimal, reproducible example
I can't reproduce the segfault but you can see the illegal read in valgrind (starting R with
R -d valgrind
)I think you might need to
PROTECT
the return value infill_window_dups_rev
. I'll make a pull request shortly which I think fixes the illegal read.Session Info
The text was updated successfully, but these errors were encountered: