Displaying 8 results from an estimated 8 matches for "r_warnings".
Did you mean:
r_warning
2003 Oct 08
1
Memmory Bugs (PR#4474)
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--43518230-584990211-1065637857=:31587
Content-Type: TEXT/PLAIN; charset=US-ASCII
I found (or rather the compiler I was using found) a few bugs in the
R-1.7.1 sources. I'm not
2011 Nov 11
1
When collected warnings exceeds 50
...(revision 57624)
+++ src/main/errors.c (working copy)
@@ -333,8 +333,11 @@
char *tr; int nc;
if(!R_CollectWarnings)
setupwarnings();
- if( R_CollectWarnings > 49 )
+ if( R_CollectWarnings > 49 ) {
+ endcontext(&cntxt);
+ inWarning = 0;
return;
+ }
SET_VECTOR_ELT(R_Warnings, R_CollectWarnings, call);
Rvsnprintf(buf, min(BUFSIZE, R_WarnLength+1), format, ap);
if(R_WarnLength < BUFSIZE - 20 && strlen(buf) == R_WarnLength)
This fix eliminates the "Invalid read" errors, but I'm unsure if it
fixes my application. I'll find out tomorrow.
J...
2019 Jul 13
2
Mitigating Stalls Caused by Call Deparse on Error
When large calls cause errors R may stall for extended periods.? This
is particularly likely to happen with `do.call`, as in this example
with a 24 second stall:
??? x <- runif(1e7)
??? system.time(do.call(paste0, list(abs, x)))? # intentional error
??? ## Error in (function (..., collapse = NULL)? :
??? ##?? cannot coerce type 'builtin' to vector of type 'character'
??? ##
2019 Jul 14
2
[External] Mitigating Stalls Caused by Call Deparse on Error
Luke, thanks for considering the issue.? I would like to
try to separate the problem into two parts, as I _think_
your comments address primarily part 2 below:
1. How can we avoid significant and possibly crippling
?? stalls on error with these non-standard calls.
2. What is the best way to view these non-standard calls.
I agree that issue 2. requires further thought and
discussion under a
2019 Jul 16
1
[External] Mitigating Stalls Caused by Call Deparse on Error
We also have a few other suggestions and wishes about backtrace
storage and display on the one hand, and display of constructed calls
on the other hand. Perhaps it would be better to open a different
wishlist item for traceback() to keep the discussions focused?
FWIW I think deparsing backtraces lazily is a great idea. Displaying 1
line per call by default in interactive sessions, while being
2019 Jul 14
0
[External] Mitigating Stalls Caused by Call Deparse on Error
This is probably best viewed in the context of other issue with
displaying calls, such as issues arising from calls constructed in
non-standard evaluation contexts. Might be good to move to a wishlist
item in bugzilla.
Best,
luke
On Sat, 13 Jul 2019, brodie gaslam via R-devel wrote:
> When large calls cause errors R may stall for extended periods.? This
> is particularly likely to happen
2019 Jul 15
0
[External] Mitigating Stalls Caused by Call Deparse on Error
Better to add this to the wishlist item. This all needs to be looked
at together, and nothing is likely to happen until after
vacation/conference season. It will disappear from everyone's radar
if it is just in R_devel.
Best,
luke
On Sun, 14 Jul 2019, brodie gaslam wrote:
> Luke, thanks for considering the issue.? I would like to
> try to separate the problem into two parts, as I
2001 Feb 17
4
Comments on R-1.2.1 builds (PR#851)
...^
cc-1552 c89: WARNING File = errors.c, Line = 161
The variable "slen" is set but never used.
int w, slen;
^
cc-1185 c89: WARNING File = errors.c, Line = 238
An enumerated type is mixed with another type.
CHAR(STRING_ELT(deparse1(VECTOR_ELT(R_Warnings, 0),0), 0)));
^
cc-1185 c89: WARNING File = errors.c, Line = 248
An enumerated type is mixed with another type.
CHAR(STRING_ELT(deparse1(VECTOR_ELT(R_Warnings,i), 0), 0)));
^
cc-1185 c89: WARNING File = errors.c, Line = 291
An enumerated...