Displaying 20 results from an estimated 400 matches similar to: "Many apologies: last post: A question about multiple(?) out of order ReleaseObject"
2014 Mar 07
0
Repost: (apologies for HTML post) A question about multiple(?) out of order ReleaseObject
Apologies, I am resending this because my emails seem to go in HTML form.
Hello,
This is a question that probably reveals my lack of understanding.
In a C function (call it cfunc), i created a SEXP, called S, and then
called R_PreserveObject on S.
I returned the SEXP to the calling R function (call it rfunc). Note, I
didn't call
R_ReleaseObject on S.
v <- .Call("cfunc")
So,
2014 Mar 06
2
A question about multiple(?) out of order ReleaseObject
Hello,
This is a question that probably reveals my lack of understanding.
In a C function (call it cfunc), i created a SEXP, called S, and then
called R_PreserveObject on S.
I returned the SEXP to the calling R function (call it rfunc). Note, I
didn't call
R_ReleaseObject on S.
v <- .Call("cfunc")
So, are the following statements correct
1. S is 'doubly' protected
2008 Feb 22
1
Calling R_PreserveObject from embedded R
Hello. This is my first post to the list, so first I'd like to thank
everybody for making and mantaining such a great product as R.
I'm writting a native binding to R from Dolphin Smalltalk. I've followed up
the examples of the documentation showing how to run R embedded, and I got
it partially working. However, I have a problem with the reference handling
of the R objects.
2010 Jan 02
1
R_PreserveObject, R_ReleaseObject : reference counting needed ?
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 to manage
garbage collection instead of the PROTECT/UNPROTECT dance. This seems to
work well, but I was wondering if there was documentation about it.
In particular, if we preserve the same SEXP twice (or more),
2010 Jan 02
3
R-devel Digest, Vol 83, Issue 2
[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
2003 Aug 24
1
declarations in non-exported headers and embedding R
Hello,
I've been using R embedded in PL/R (R procedural language handler for
PostgreSQL, http://www.joeconway.com/plr/) very successfully for several
months now. A sincere "thank you" goes to the R development team for
such a great product.
I have a question I'm hoping someone here can help me with. In order to
get the required functionality out of PL/R, I've had to
2017 Sep 21
2
calling R API functions after engine shutdown
Hi!
We?ve recently come across an example where a package (minqa) creates an Rcpp Function object in a static variable.
This causes R_ReleaseObject to be called by the destructor at a very late point in time - as part of the system exit function:
static Function cf("c");
I?m wondering if that is considered to be ?safe??
Is the R engine supposed to stay in a state where calls to API
2017 Sep 21
0
calling R API functions after engine shutdown
Calling R_ReleaseObject in a C++ destructor is not reliable - it can be
bypassed by a non-local return, such as an error. Generally in R one
cannot use C++ destructors reliably for anything that the R runtime
wouldn't do on its own in case of a non-local return.
A destructor that calls just UNPROTECT, in a way that balances out the
protection stack (e.g. Rcpp Shield), is safe because R
2008 Jul 20
1
garbage collection, "preserved" variables, and different outcome depending on "--verbose" or not
Dear list,
While trying to identify the root of a problem I am having with
garbage collected variables,
I have come across the following oddity: depending on whether --verbose is set
or not, I obtain different results.
I have made a small standalone example to demonstrate it.
The example is very artificial, but I had a hard time reproducing
reliably the problem.
So when I do: (the content of
2005 Sep 18
0
Updated rawConnection() patch
Here's an update of my rawConnection() implementation. In addition to
providing a raw version of textConnection(), this fixes two existing
issues with textConnection(): one is that the current textConnection()
implementation carries around unprotected SEXP pointers, the other is
a performance problem due to prolific copying of the output buffer as
output is accumulated line by line.
This new
2009 Nov 30
1
:Re: PROTECT and OCaml GC.
>>> On Nov 28, 2009, at 7:50 PM, Guillaume Yziquel wrote:
>>>
>>> FWIW what I think you should be really looking at is
>>> R_PreserveObject/R_ReleaseObject.
>
> OK. Thanks.
>>> I would suggest looking at the many other R embeddings in other
>>> languages that already exist since I don't think you approach is
>>> very viable
2014 Mar 05
1
[PATCH] Code coverage support proof of concept
Hello,
I submit a patch for review that implements code coverage tracing in
the R interpreter.
It records the lines that are actually executed and their associated
frequency for which srcref information is available.
I perfectly understands that this patch will not make its way inside R
as it is, that they are many concerns of stability, compatibility,
maintenance and so on.
I would like to have
2020 Aug 24
0
[PATCH v6 48/76] x86/entry/64: Add entry code for #VC handler
From: Joerg Roedel <jroedel at suse.de>
The #VC handler needs special entry code because:
1. It runs on an IST stack
2. It needs to be able to handle nested #VC exceptions
To make this work the entry code is implemented to pretend it doesn't
use an IST stack. When entered from user-mode or early SYSCALL entry
path it switches to the task stack, if entered from kernel-mode it
tries
2008 May 24
0
[ wxruby-Bugs-20346 ] can not run wxruby-1.9.7 under ruby1.9.0 in linux
Bugs item #20346, was opened at 2008-05-24 12:02
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=218&aid=20346&group_id=35
Category: Compile/build
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: can not run wxruby-1.9.7 under ruby1.9.0 in linux
Initial Comment:
superman minimal # ruby
2009 Oct 25
2
wxruby2.so: [BUG] Segmentation fault on require 'wx'
Hi --
I am trying to get ruby 1.9 to run on my Windows Vista Ultimate computer
with and Intel 32 bit processor and all OS updates applied.
I installed ruby 1.9 on October 23, 2009 using the zip file
(ruby-1.9.1-p129-i386-mswin32.zip) and the instructions located at:
http://blog.orangecabin.com/2009/05/install-ruby-1-9-on-windows-using-zip-binary/.
I was able to run several simple scripts. So far
2005 Apr 12
5
How allocate STRSXP outside of gc
Hi,
I am trying to figure a way to allocate a string SEXP so that gc() won't
ever collect it.
Here is a little bit of a background. Suppose I want to write a
.Call-callable function that upon each call returns the same value, say
mkChar("foo"):
SEXP getFoo() {
return mkChar("foo");
}
The above implementation doesn't take advantage of the fact that
2012 Aug 18
0
hosting with speedyrails
hello everyone,
original app: rails 3.1.1
ruby 1.9.2p180 (2011-02-18 revision 30909) [i686-linux]
I try to host my app into speedyrails using capistrano.
I host my sample application and running. I just get only one error like my assets
were not precompiled. then i solve that by adding "load ''deploy/assets''"
this code in my deploy receipt.
and my
2008 May 07
1
[BioC] RCurl loading problem with 64 bit linux distribution
Martin,
Well, thanks for jumping in! We need all the help we can get ;)
I changed the execute bit as you suggested and recompiled, no luck, still
the same error message.
Below is the output you wanted me to look at, its a bit beyond me so I
include both a brief grep summary and then the whole enchilada. I do note
that my output is different from yours, but I'm not sure how to interpret.
I
2008 May 07
1
[BioC] RCurl loading problem with 64 bit linux distribution
Martin,
Well, thanks for jumping in! We need all the help we can get ;)
I changed the execute bit as you suggested and recompiled, no luck, still
the same error message.
Below is the output you wanted me to look at, its a bit beyond me so I
include both a brief grep summary and then the whole enchilada. I do note
that my output is different from yours, but I'm not sure how to interpret.
I
2020 Aug 31
1
[PATCH v6 48/76] x86/entry/64: Add entry code for #VC handler
On Mon, Aug 24, 2020 at 10:54:43AM +0200, Joerg Roedel wrote:
> @@ -446,6 +448,82 @@ _ASM_NOKPROBE(\asmsym)
> SYM_CODE_END(\asmsym)
> .endm
>
ifdeffery pls...
> +/**
> + * idtentry_vc - Macro to generate entry stub for #VC
> + * @vector: Vector number
> + * @asmsym: ASM symbol for the entry point
> + * @cfunc: C function to be called
> + *
> + * The macro