search for: rvsnprintf

Could Rvsnprintf (in src/main/errors.c) be added to the R API with prototype in include/R_ext/Print.h say? Here's my problem. I'm trying to write some code that is not totally tied to R. Hence I want R style error messaging to be isolated in a small module. I do not want #include <R.h> and calls t...

...uot; ) I can?t access the error. And this boils down to this call: gotoExitingHandler(R_NilValue, call, entry); inside vsignalError : static void vsignalError(SEXP call, const char *format, va_list ap) { char localbuf[BUFSIZE]; SEXP list, oldstack; oldstack = R_HandlerStack; Rvsnprintf(localbuf, BUFSIZE - 1, format, ap); while ((list = findSimpleErrorHandler()) != R_NilValue) { char *buf = errbuf; SEXP entry = CAR(list); R_HandlerStack = CDR(list); strncpy(buf, localbuf, BUFSIZE - 1); /* Rvsnprintf(buf, BUFSIZE - 1, format, ap);*/ buf[BUFSIZE - 1] = 0; if (IS_CALLING_E...

...(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. Jeff

...red libraries . done Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x5f4d4550 0x90002f48 in strlen () (gdb) where #0 0x90002f48 in strlen () #1 0x9000d7d0 in __vfprintf$LDBL128 () #2 0x900273cc in vsnprintf$LDBL128 () #3 0x0108ea1c in Rvsnprintf (buf=0xbfff35f4 "B", size=1000, format=0x3 <Address 0x3 out of bounds>, ap=0x34 <Address 0x34 out of bounds>) at ../../../../R-2.3.0/src/main/errors.c:211 #4 0x01092e68 in Rf_warning (format=0x3 <Address 0x3 out of bounds>) at ../../../../R-2.3.0/src/main/errors.c:223 #...