Dear R developers,
it seems the stack checking issue with embedded applications is not fully
resolved, yet. The problem arises, when multiple threads are involved. I.e.
the case, where R is run in a separate thread of the main application. In
this case, the call to (unix/system.c)
On Tue, 11 Apr 2006, A.J. Rossini wrote:
(This is under SBCL, i.e. satisfying Duncan's conjectures -- as soon
as I fix a few things (i.e. undoing CommonLispStat/R's threading which
is a bit SBCL specific, I'll try under CLISP, ECL, and CMUCL to
verify/check).
Also, according to
I'm pretty sure that we've fixed that problem. (I'm merging 2 different
CL/R trees together, one of which is Cyrus's). An alternative fix patched
R to undo that, but that's not kosher.
best,
-tony
On 4/12/06, Thomas Lumley [EMAIL PROTECTED] wrote:
On Tue, 11 Apr 2006, A.J. Rossini wrote:
On 4/11/06, Prof Brian Ripley [EMAIL PROTECTED] wrote:
On Tue, 11 Apr 2006, A.J. Rossini wrote:
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been experiencing some interesting stack warnings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony.
Just to eliminate things, is the host application
in which R is being embedded doing anything with
the stack, e.g. some lisp system playing with threads
via manipulating the stack?
D.
A.J. Rossini wrote:
I will say this first -- I
Yep, bingo. That's what I'm thinking, too. Except that it's supposed
to be protected at my end.
Supposed to.
On 4/11/06, Duncan Temple Lang [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony.
Just to eliminate things, is the host application
in which R is
On Tue, 11 Apr 2006, A.J. Rossini wrote:
On 4/11/06, Prof Brian Ripley [EMAIL PROTECTED] wrote:
On Tue, 11 Apr 2006, A.J. Rossini wrote:
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been experiencing
On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
I've been experiencing some interesting stack warnings recently
when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
series. In particular, I'm getting warnings of Error: C stack
usage is too close to the limit before
Simon Urbanek wrote:
On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
I've been experiencing some interesting stack warnings recently
when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
series. In particular, I'm getting warnings of Error: C stack
usage is too close to the
On 4/12/06, Simon Urbanek [EMAIL PROTECTED] wrote:
On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
I've been experiencing some interesting stack warnings recently
when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
series. In particular, I'm getting warnings of Error: C stack
On Tue, 11 Apr 2006, Jeffrey Horner wrote:
Simon Urbanek wrote:
On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
I've been experiencing some interesting stack warnings recently
when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
series. In particular, I'm getting warnings of
11 matches
Mail list logo
