Displaying 20 results from an estimated 156 matches for "dotcode".
1997 Jul 30
0
R-beta: Query: installing 0.50-a1 on Solaris 2.5.1
Can anyone spot the problem here. Following is an edited script of the install
session. The gist is:
* syntax error in original src/main/dotcode.c
Easily remedied (or at least, such that compiles without error message ... )
change line 449-450 (two lines preceding return)
#ifdef HAVE_F77_UNDERSCORE
if(PRIMVAL(op)) {
*q++ = '_';
*q = '\0';
#endif
}
return mkString(buf);
}
to
}
#endif...
2005 Jun 02
2
dotcode typo? (PR#7917)
...>Reid Huntsinger
>>
>>-----Original Message-----
>>From: r-devel-bounces@stat.math.ethz.ch
>>[mailto:r-devel-bounces@stat.math.ethz.ch] On Behalf Of Huntsinger, Reid
>>Sent: Thursday, June 02, 2005 12:33 PM
>>To: r-devel@stat.math.ethz.ch
>>Subject: [Rd] dotcode typo?
>>
>>
>>I ran across the following in the R-2.0.1 source, src/main/dotcode.c, in the
>>function resolveNativeRoutine(), lines 146-163. Line 152 looks like a typo:
>>here are lines 149-155
>>
>> if(!*fun) {
>> if(dll.type != FILENAME) {
&g...
2001 Jul 13
7
too many arguments in foreign function call
...ode) that needs a lot of arguments. When I use .Fortran,
I get the message 'too many arguments in foreign function call'.
Neither the help page for .Fortran (actually Foreign) nor "Writing R
Extensions" explains how many arguments are too many.
Looking at the code in src/main/dotcode.c, I see that MAX_ARGS is set to
65.
While it is possible to work around this limitation, it seems
arbitrary. I propose increasing the arbitrary value to 255 and adding
appropriate documentation to the Foreign manual page.
Any objections/comments?
-Greg
-----Patch-Starts-Here------
diff -ur...
2001 Jul 13
7
too many arguments in foreign function call
...ode) that needs a lot of arguments. When I use .Fortran,
I get the message 'too many arguments in foreign function call'.
Neither the help page for .Fortran (actually Foreign) nor "Writing R
Extensions" explains how many arguments are too many.
Looking at the code in src/main/dotcode.c, I see that MAX_ARGS is set to
65.
While it is possible to work around this limitation, it seems
arbitrary. I propose increasing the arbitrary value to 255 and adding
appropriate documentation to the Foreign manual page.
Any objections/comments?
-Greg
-----Patch-Starts-Here------
diff -ur...
2017 Feb 22
0
Crash in the latest release
...SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*,
SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*) (in /home/therneau/Rlib/lme4/libs/lme4.so)
==31901== by 0xD8727F1: merPredDCreate (in /home/therneau/Rlib/lme4/libs/lme4.so)
==31901== by 0x80C0B9E: R_doDotCall (dotcode.c:648)
==31901== by 0x80C159F: do_dotcall (dotcode.c:1252)
==31901== by 0x80FFABA: Rf_eval (eval.c:728)
==31901== by 0x810308A: do_set (eval.c:2579)
==31901== by 0x80FF907: Rf_eval (eval.c:700)
==31901== Address 0xe310828 is 0 bytes after a block of size 2,408 alloc'd
==31901==...
2017 Feb 22
0
[Lme4-authors] Crash in the latest release
...PREC*, SEXPREC*, SEXPREC*,
> SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*, SEXPREC*,
> SEXPREC*) (in /home/therneau/Rlib/lme4/libs/lme4.so)
> ==31901== by 0xD8727F1: merPredDCreate (in
> /home/therneau/Rlib/lme4/libs/lme4.so)
> ==31901== by 0x80C0B9E: R_doDotCall (dotcode.c:648)
> ==31901== by 0x80C159F: do_dotcall (dotcode.c:1252)
> ==31901== by 0x80FFABA: Rf_eval (eval.c:728)
> ==31901== by 0x810308A: do_set (eval.c:2579)
> ==31901== by 0x80FF907: Rf_eval (eval.c:700)
> ==31901== Address 0xe310828 is 0 bytes after a block of size 2,408...
1997 Apr 11
1
R-beta: Linux Installation Problem
A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 7478 bytes
Desc: not available
Url : https://stat.ethz.ch/pipermail/r-help/attachments/19970411/ce9d665d/attachment.ksh
2005 Jul 19
2
segfault with grid and null unit (PR#8014)
...c:464)
5 grid.so 0x060ca888 calcViewportTransform + 1296
(viewport.c:356)
6 grid.so 0x060be0a0 doSetViewport + 256 (grid.c:200)
7 grid.so 0x060be5ac L_setviewport + 76 (grid.c:311)
8 libR.dylib 0x00249318 do_dotcall + 652 (dotcode.c:770)
9 libR.dylib 0x0024cc7c do_dotcallgr + 80 (dotcode.c:1450)
10 libR.dylib 0x00263b24 Rf_eval + 1536 (eval.c:405)
11 libR.dylib 0x00265b1c do_set + 224 (eval.c:1309)
2009 Jun 06
1
Qs on calling R from C
Consider the following simple C program:
/*** hello_r.c ***/
#include <Rinternals.h>
SEXP hello() {
return mkString("Hello, world!\n");
}
int main(void) {
SEXP x = hello();
return x == NULL; /* i.e. 0 on success */
}
This program segfaults:
% myR/bin/R CMD LINK gcc -I./R-2.9.0/src/include -L./myR/lib64/R/lib -lR
hello_r.c -o hello_r > /dev/null
% hello_r
zsh:
2015 Feb 05
2
Invalid read of size 8
...quot;\n\n");
}
I see that the values of MatCovInv[k] have changed.
Valgrind shows the following error on the second block of Rprintf:
Later Cov Extra 3 0x107df7fb8
==954== Invalid read of size 8
==954== at 0xA92D599: NPHDPHMM (in /Users/NPHDPHMM.so)
==954== by 0x8632A: do_dotcall (dotcode.c:652)
==954== by 0xB036A: Rf_eval (eval.c:657)
==954== by 0xBE8C0: do_set (eval.c:2028)
==954== by 0xB0404: Rf_eval (eval.c:629)
==954== by 0xBE3C4: do_begin (eval.c:1638)
==954== by 0xB0404: Rf_eval (eval.c:629)
==954== by 0xBB95D: Rf_applyClosure (eval.c:1038)
==954== by 0xB...
2006 Dec 13
2
capturing value of C or Fortran function
Re: src/main/dotcode.c:do_dotCode()
The value, if there is one, of a function called by .C or .Fortran is not
captured, so one needs a wrapper. To avoid that, the user would have to
declare that there is a value, specify its type, and supply an R variable
to hold the value. Presumably, all of these could be combined...
1999 May 17
1
minor installation problems
...duced the correct result, so
I don't know where this zero size problem came from.
2. After the final linking of R via
g77 -o ../../bin/R.binary arithmetic.o array.o attrib.o bind.o
builtin.o character.o coerce.o colors.o complex.o context.o cov.o
cum.o debug.o deparse.o deriv.o devices.o dotcode.o dstruct.o
duplicate.o envir.o errors.o eval.o format.o fourier.o gram.o
gram-ex.o graphics.o iosupport.o list.o logic.o main.o match.o
memory.o model.o names.o objects.o optimize.o options.o par.o paste.o
platform.o plot.o plot3d.o plotmath.o print.o printarray.o
printvector.o printutils.o random...
1999 May 17
1
minor installation problems
...duced the correct result, so
I don't know where this zero size problem came from.
2. After the final linking of R via
g77 -o ../../bin/R.binary arithmetic.o array.o attrib.o bind.o
builtin.o character.o coerce.o colors.o complex.o context.o cov.o
cum.o debug.o deparse.o deriv.o devices.o dotcode.o dstruct.o
duplicate.o envir.o errors.o eval.o format.o fourier.o gram.o
gram-ex.o graphics.o iosupport.o list.o logic.o main.o match.o
memory.o model.o names.o objects.o optimize.o options.o par.o paste.o
platform.o plot.o plot3d.o plotmath.o print.o printarray.o
printvector.o printutils.o random...
2002 Nov 11
2
R 1.6.1: help with debugging error in RunGenCollect(), R_gc_internal
...n ?? ()
#1 0x080bcae7 in RunGenCollect (size_needed=6777) at memory.c:1286
#2 0x080bdaa0 in R_gc_internal (size_needed=6777) at memory.c:1859
#3 0x080bd729 in Rf_allocVector (type=13, length=13554) at memory.c:1722
#4 0x08090a71 in CPtrToRObj (p=0x98db958, arg=0x98b29f8, Fort=1, type=13)
at dotcode.c:209
#5 0x080933cb in do_dotCode (call=0x89f3880, op=0x8222154, args=0x833b380,
env=0x8346e90) at dotcode.c:1907
#6 0x080a035d in Rf_eval (e=0x89f3880, rho=0x8346e90) at eval.c:427
#7 0x080a195a in do_set (call=0x89f390c, op=0x8218610, args=0x89f38b8,
rho=0x8346e90) at eval.c:1102
#8...
2005 Dec 28
2
.Call not counting parameters consistently (PR#8450)
...This happens in Windows versions of R-patched and R-devel. Charlie
Geyer was bitten by this in his fuzzyRankTests package (version 0.3),
which fails check because of it on Windows, but not on Unix. I haven't
done any testing on Unix.
I've traced into the do_dotcall function in src/main/dotcode.c, and I
see that on the second call the "symbol.symbol.call" member is NULL, so
no test is done, but I don't see why this is happening. The
resolveNativeRoutine function does some strange stuff.
Duncan Murdoch
1999 Feb 02
0
Suggestion
...C functions that build
R objects. Eventually, it would be best to have an API to standardize
the process of building R object too...
I'd like to see .RC added to the standard R distribution. Right now, I'm
applying my patch every time I upgrade R. Here is my diff
diff -r R-0.63/src/main/dotcode.c R-0.63.orig/src/main/dotcode.c
264,286d263
< SEXP do_dotRCode(SEXP call, SEXP op, SEXP args, SEXP env)
< {
< DL_FUNC fun;
< char buf[128], *p, *q, *vmax;
< SEXP retval;
<
< vmax = vmaxget();
< op = CAR(args);
< if (!isString(op)) erro...
2000 May 22
1
character arguments with call_R (PR#552)
character arguments with call_R do not work except in the first
position. (In other positions, they just yield a single blank
character.)
The error is at line 1858 of dotcode.c which should be changed from
STRING(CAR(pcall))[i]=s;
to
STRING(CAR(pcall))[0]=s;
Jim
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[...
2005 May 12
0
Patch to address (PR#7853) -- tested briefly, seems to
.... We will do that
for 2.2.0.
Two hints (more for R-devel than just you).
1) Please provide a patch against the current sources, not 2.0.0. (it
worked, with a bit of fiddling).
2) Please _attach_ patches, as your mailer wrapped this one.
On Thu, 12 May 2005 keithf@amnis.com wrote:
> --- dotcode.c 2004-09-05 02:31:57.000000000 -0700
> +++ /usr/local/src/R-2.0.0/src/main/dotcode.c 2005-05-11
> 12:24:11.000000000 -0700
> @@ -190,6 +190,7 @@
> static void *RObjToCPtr(SEXP s, int naok, int dup, int narg, int Fort,
> const char *name, R_toCConverter **converter,
>...
1998 Mar 27
1
R-beta: Problems during compilation of R for Solaris 2.6
...compilation of R (version 0.61.2) for Solaris 2.6.
I have installed the gcc 2.8.0 version.
>> gcc -o R.binary arithmetic.o array.o attrib.o bind.o builtin.o character.o >> coerce.o colors.o complex.o context.o cov.o cum.o dataframe.o debug.o >> deparse.o deriv.o dotcode.o dstruct.o duplicate.o envir.o errors.o eval.o >> format.o fourier.o iosupport.o gram.o list.o logic.o main.o match.o memory.o >> model.o names.o objects.o optimize.o options.o par.o paste.o plot.o plot3d.o >> plotmath.o print.o printarray.o printvector.o...
2010 Oct 27
2
must .Call C functions return SEXP?
...what's going on here
and so don't trust it. The list SEXP I am returning was allocated by
R, not by my C code, so why does it make any difference whether my C
function returns it or not?
>From "src/main/names.c" I see that .Call is implemented by do_dotcall
in "src/main/dotcode.c". I don't necessarily understand what that
really does, but AFAICT if my C function returns nothing, the
do_dotcall's retval should simply remain set to R_NilValue, which
should be fine.
I must be misunderstanding something here, but I don't know what, and
would definitely appr...