search for: unprotecting

Dear R experts, In all R functions written in C one must unprotect result before returning them: { ... UNPROTECT(1) /* unprotecting `ans' */ return ans; } Why does one shure that memory occupied by `ans' won't be used by R immediately after unprotecting? Ok, is the next construction also absolutely safe? { ... UNPROTECT(1) /* unprotecting `ans' */ PROTECT( val = ans ) ......

Hi, I'm getting messages like res_srtp.c:395 ast_srtp_unprotect: SRTP unprotect failed with replay check failed (index too old), retrying == SRTP unprotect failed on SSRC 576693764 because of authentication failure 10 == SRTP unprotect failed on SSRC 576693764 because of authentication failure 160 [...] ... after a couple minutes during voice calls after which the connection is being

There is a problem with the patch I sent out yesterday. The patches for the glm code are applied in the wrong place. I have removed the patch file and will have a real one available latter today. Ross =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help",

Hi, I'm troubleshooting some native code on Windows that very occationally (and semi-randomly) crashes R. Already looked at "everything", I just want to double check that it is safe to UNPROTECT() allocated variables as soon as they are assigned to, say, a PROTECTed list. >From (R v2.3.0) Section 5.7.1 "Handling the effects of garbage collection" in "Writing R

Consider the C (or C++) code called from the .Call interface: SEXP foo() { SEXP *p = PROTECT(allocVector(REALSXP, 10)); ... UNPROTECT(1); return p; } Why is there no danger that the allocated memory will be garbage collected after the UNPROTECT, but before the return of p? I have used code like this for some time and have never had a problem, but I'm not sure if/why it is guaranteed

...ts) on a way to simplify debugging such problem in addition to using gdb, please? I thought about temporarily defining macros such as #define DEBUG_Protect(x) PROTECT(x); fprintf(stderr, "Protecting in %s, l: %d\n", __FILE__, __LINE__) #define UNDEBUG_Protect(x) fprintf(stderr, "Unprotecting %d in %s, l:, %d \n", x , __FILE__, __LINE__); UNPROTECT(x); and then replace all calls temporarily in the package source. But there must be a better way... Thank you very much (and my appologies, if this sounds odd to more experineced c programmers ;) ) Michael

Hello! Ater several successful SRTP-enabled calls with SRTP set to Mandatory, asterisk starts to give the following warnings in Log: WARNING[13714] res_srtp.c: SRTP unprotect: authentication failure (continiously) and client hears no sound. After i restart the client program it works fine again for a while. Then the same warning again. Asterisk 1.8.1.1, RealTime engine, sip peer has

On Thu, Jan 16, 2020 at 11:35 AM hw <hw at gc-24.de> wrote: > On Tuesday, January 14, 2020 5:29:04 PM CET hw wrote: > > Hi, > > > > I'm getting messages like > > > > > > res_srtp.c:395 ast_srtp_unprotect: SRTP unprotect failed with replay > check > > failed (index too old), retrying == SRTP unprotect failed on SSRC > 576693764 > >

I want to write an R function using R's C interface that takes a 2-column matrix of increasing, non-overlapping integer intervals and returns a list with those intervals plus some added intervals, such that there are no gaps. For example, it should take the matrix rbind(c(5L, 6L), c(7L, 10L), c(20L, 30L)) and return list(c(5L, 6L), c(7L, 10L), c(11L, 19L), c(20L, 30L)). Because the output is

Dear R developers, I've just encountered one "feature" of R-C extensions. If it is known, I would be thankful for any hints why it works this way (I found the way around, which is also mentioned here, but maybe it is not the best one). If it is however unknown, it might be considered for a "wish list". Consider a simple "aka" C function (the original

Hi! I want to return a matrix. The code does the R interfacing. This version does it fine. SEXP ans,dim; PROTECT(ans = NEW_NUMERIC(count*2)); memcpy(NUMERIC_POINTER(ans),result,count*sizeof(double)); memcpy(&(NUMERIC_POINTER(ans)[count]),occur,count*sizeof(double)); /** PROTECT(dim=NEW_INTEGER(2)); INTEGER_POINTER(dim)[0]=2; INTEGER_POINTER(dim)[1]=count;

On Tuesday, January 14, 2020 5:29:04 PM CET hw wrote: > Hi, > > I'm getting messages like > > > res_srtp.c:395 ast_srtp_unprotect: SRTP unprotect failed with replay check > failed (index too old), retrying == SRTP unprotect failed on SSRC 576693764 > because of authentication failure 10 == SRTP unprotect failed on SSRC > 576693764 because of authentication failure

Am I opening myself to some security vulnerability if I unprotect the Controller classes'' redirect methods? I merrily wrote a (specific to my university) authentication filter as a separate class. As part of the authentication process it needs to re-direct the user to a university server to log in. This all works fine except that the redirect_to methods of a controller are all

Hello. In the writing of my OCaml-R binding, I'm sort of confused when it comes to the use of the PROTECT and UNPROTECT macros. Basically, I have C stub functions that are in charge of calling R for everything. Here's a simple example: > CAMLprim value r_findvar (value symbol) { > /* The findVar function is defined in envir.c. It looks up a symbol > in an environment.

there is my code,  expect return value  is a data frame but R say it is list: SEXP Julia_R_MD_NA_DataFrame(jl_value_t* Var) {  SEXP ans,names,rownames;  char evalcmd[4096];  int i;  const char* dfname="DataFrameName0tmp";  jl_set_global(jl_main_module, jl_symbol(dfname), (jl_value_t*)Var);  //Get Frame cols   sprintf(evalcmd,"size(%s,2)",dfname);  jl_value_t*

Hello, this is my first wine-time, and a lot of winprograms run "out of the box" Great! But there is a little DOS-program which does not run. Where can I look for the error? Thanks for any hint. geo@toso:~> wine "c:\Program Files\saft\saft.exe" Warning: unprotecting the first 64KB of memory to allow real-mode calls. NULL pointer accesses will no longer be caught. fixme:int:DOSVM_Int10Handler Get Font Information - Not Supported fixme:int:DOSVM_Int10Handler Select Active Display Page (0) - Not Supported Beste Gr??e Jochen ___________________...

https://bugzilla.mindrot.org/show_bug.cgi?id=1909 Summary: "WARNING: UNPROTECTED PRIVATE KEY FILE!" warning needs an actionable step Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: ssh

Hello, I call a function via .Call passing to it a raw vector(D) and an integer(I) The vector is a series K1,KData1, V1,VData1, K2, KData2, ... where the integer K1 is the length of Data1 and similarly for Ki (wrt Datai)(similarly for V*) There 2*I such pairs( (Ki,KDatai), (Vi,VDatai)) The numbers Ki(and Vi) are written in network order. I am returning a list of I elements each element a

As I mentioned in my previous message about speeding up evalList, I've been looking at ways to speed up the R interpreter. One sees in the code many, many calls of PROTECT, UNPROTECT, and related functions, so that seems like an obvious target for optimization. Indeed, I've found that one can speed up the interpreter by about 10% by just changing these. The functions are actually macros

[Disclaimer: what is below reflects my understanding from reading the R source, others will correct where deemed necessary] On 1/2/10 12:00 PM, r-devel-request at r-project.org wrote: > > Hello, > > We are currently making lots of changes to Rcpp (see the open Rcpp > mailing list if interested [1] in the details). > > We are now using [2] R_PreserveObject and R_ReleaseObject