"Ole F. Christensen" <[EMAIL PROTECTED]> writes:
> Brain, Thank you very much for your help.
*
You seem to be using call-by-value semantics rather than
call-by-name...
--
O__ Peter Dalgaard Øster Farimagsgade 5, Entr.B
c/ /'_ --- Dept. of Biostatistics PO Box
Well, valgrind helps a lot more here: it points at lines 2131 and 2135-6
of eigen.f, and using gdb shows those are called with NA = 0.
So it is a bug in EISPACK, and easy enough to fix -- now done.
On Tue, 3 Jan 2006, Ole F. Christensen wrote:
> Brain, Thank you very much for your help.
> Using
Brain, Thank you very much for your help.
Using gctorture I was able to produce a simple function call showing the
problem.
Gm <- rbind(c(-0.3194373786, 0.2444066686, 0.0428108831, 3.221983e-02),
c(0.0002071301, -0.0003282719, 0.0001211418,
5.128830e-12),
Try valgrind. That is reporting use outside arrays in rg, that is the
non-complex case of eigen().
Otherwise, using gctorture(TRUE) will help precipitate the error.
On Mon, 2 Jan 2006, Ole F. Christensen wrote:
>
> Dear subscribers of R-devel
>
> I am experiencing that R crashes (further detai
Dear subscribers of R-devel
I am experiencing that R crashes (further details are given below) in
some complex matrix calculations when EISPACK=TRUE has been specified in
eigen().
I discovered the behaviour some months ago just after the
release of R-2.2.0, and it has been lying on my desk since
