Displaying 3 results from an estimated 3 matches for "corolary".
Did you mean:
corollary
2018 Aug 09
2
SIGSEGV in R_RunWeakRefFinalizer, object allocated with Rcpp
...ows, but not on Linux (then I built the example in my
initial email to confirm it wasn't simmer's fault). So given that,
from your explanation, I should expect a segfault here, the question
is: what on Earth does (or does not) R on Linux do to avoid
segfaulting compared to Windows? :) And a corolary would be, can't R
on Windows do the same?
Regards,
I?aki
El jue., 9 ago. 2018 a las 21:13, <luke-tierney at uiowa.edu> escribi?:
>
> On Thu, 9 Aug 2018, Dirk Eddelbuettel wrote:
>
> >
> > On 9 August 2018 at 20:37, Tomas Kalibera wrote:
> > | So to answer your...
2018 Aug 10
0
SIGSEGV in R_RunWeakRefFinalizer, object allocated with Rcpp
...x (then I built the example in my
> initial email to confirm it wasn't simmer's fault). So given that,
> from your explanation, I should expect a segfault here, the question
> is: what on Earth does (or does not) R on Linux do to avoid
> segfaulting compared to Windows? :) And a corolary would be, can't R
> on Windows do the same?
>
> Regards,
> I?aki
>
> El jue., 9 ago. 2018 a las 21:13, <luke-tierney at uiowa.edu> escribi?:
>> On Thu, 9 Aug 2018, Dirk Eddelbuettel wrote:
>>
>>> On 9 August 2018 at 20:37, Tomas Kalibera wrote:
>&...
2018 Aug 09
4
SIGSEGV in R_RunWeakRefFinalizer, object allocated with Rcpp
On 9 August 2018 at 20:37, Tomas Kalibera wrote:
| So to answer your original question, this could probably be handled in
| Rcpp,
Hm. Why do you say that / what did you have in mind?
Recall that we do not alter SEXPs or introduce additional additional
reference counters -- because we do not think that altering the basic R API
for such calls would be a wise strategy. So we do more or less what