Thanks Duncan for helping me along the way. I am working in OSX,
Linux, and Windows, and gdb is helping me trace it along to what
appears to be an endless processor intensive loop in sys-std.c .
Below, I have pasted the output. All files are closed as verified by
lsof. There is absolutely no stdio
Thanks a lot guys. I'll try out what you suggested.
Thanks,
RJ
On Thu, Mar 24, 2011 at 8:46 AM, Dirk Eddelbuettel e...@debian.org wrote:
On 24 March 2011 at 08:08, Duncan Murdoch wrote:
| On 11-03-23 7:35 PM, Rob Anderson wrote:
| Hi All,
|
| I am trying to write a source-to-source
Dear list,
I have another (again possibly boneheaded) puzzle about importing,
again encapsulated in a nearly trivial package. (The package is posted
at http://www.math.mcmaster.ca/bolker/misc/coefsumtest_0.001.tar.gz.)
The package consists (only) of the following S3 method definitions:
On 03/26/2011 11:14 AM, Ben Bolker wrote:
Dear list,
I have another (again possibly boneheaded) puzzle about importing,
again encapsulated in a nearly trivial package. (The package is posted
athttp://www.math.mcmaster.ca/bolker/misc/coefsumtest_0.001.tar.gz.)
The package consists
On 11-03-26 02:52 PM, Martin Morgan wrote:
On 03/26/2011 11:14 AM, Ben Bolker wrote:
Dear list,
I have another (again possibly boneheaded) puzzle about importing,
again encapsulated in a nearly trivial package. (The package is posted
Dear list,
I have been checking my package ('analogue') using R2.13-0-alpha
(details of exact svn version appended below) and the R CMD check
procedure is generating an error rebuilding a vignette in the package,
which raises a NOTE in the check.
The log printed to screen during check shows:
On Wed, Mar 23, 2011 at 6:35 PM, Rob Anderson rkjan...@gmail.com wrote:
Hi All,
I am trying to write a source-to-source compiler for R. I am trying to
leverage the R parser code for the purpose. I am trying to transform the
SEXP returned from the parser into an AST for our own Ruby embedded
Current core/Recommended Matrix package (0.999375-48) has been segfaulting
against R 2.13-alpha/2.14-trunk for the last week or so (since R-2.13 was
branched, when I started trying) when run with R CMD check --use-gct:
--
pkgname - Matrix
source(file.path(R.home(share), R,
The pattern (I can make a simple example if needed):
source(x.R)
options(error=recover)
x - ...
f(x) # f() from x.R
(subscript bounds error, now in recover())
Selection: 1
Browse[1] where
In the output from where, there should be information on the line
number at
You seem to have missed the force of the warning in 'Writing R
Extensions'.
If you include *any* Fortrann I/O in your package code, you are at
risk from it interfering with C I/O, whether or not that Fortran I/O
is called.
On some platforms with gfortran, merely loading such a package's
10 matches
Mail list logo