William Dunlap wrote:
Running his example under valgrind (a memory misuse checker on Linux)
does show it using memory it should not be using in the optimization C
code
around where it is copying the gradient vector. The
==10916== Invalid read of size 1
==10916==at 0x400686D: memcpy (mc_r
William Dunlap wrote:
From: r-devel-boun...@r-project.org
[mailto:r-devel-boun...@r-project.org] On Behalf Of Ben Bolker
Sent: Monday, August 10, 2009 12:52 PM
To: r-devel@r-project.org
Subject: Re: [Rd] Bug in nlm, found using sem; failure in
several flavors (PR#13883)
A wild guess
> From: r-devel-boun...@r-project.org
> [mailto:r-devel-boun...@r-project.org] On Behalf Of Ben Bolker
> Sent: Monday, August 10, 2009 12:52 PM
> To: r-devel@r-project.org
> Subject: Re: [Rd] Bug in nlm, found using sem; failure in
> several flavors (PR#13883)
>
>
>
A wild guess, based on some recent "non-deterministic" behavior in
lme4: could this be driven by a bug in optimized linear algebra libraries
(BLAS/LAPACK)? (Unfortunately, I'm not clear on how to check the versions
of BLAS/LAPACK being used and whether they are subject to bugs,
but perhaps so
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--1660387551-150661043-1249684349=:2997
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Hi
