{This was sent to me, MM, only, but for completeness should
have gone back to R-devel.
Further: I now *have* added Marie B to the members'of "R bugzilla"
-- M.Maechler}
I had already read the R bug reporting guide and I'm sure it is a bug.
The bug occurs when the u
> Boehnstedt, Marie
> on Fri, 3 Mar 2017 10:23:12 + writes:
> Dear all,
> I have found a bug in nlm() and would like to submit a report on this.
> Since nlm() is in the stats-package, which is maintained by the R Core
team, bug reports should be submitted to R's Bugzi
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
Hi Jeff,
As mentioned in my message, I *did* replicate on another platform.
One platform was running linux in a VM, the other running MacOSX, on two
different physical machines. The problem did not replicate on a PowerPC
box, so if it is a bug with intel chips, I think it's also appropriate t
Adam,
It seems that your attachment didn't make it through.
That aside, my experience with strange errors like those (random type
not implemented ones) has been that you may be looking at a memory
problem on you machine. Given that you can't replicate on another
platform (and the .csv file didn't
Adam,
It seems that your attachment didn't make it through.
That aside, my experience with strange errors like those (random type
not implemented ones) has been that you may be looking at a memory
problem on you machine. Given that you can't replicate on another
platform (and the .csv file didn't
10 matches
Mail list logo
