It seems that Mrecv() tries to write on the status arg, even when it
is STATUS_IGNORE. Looking at the sources (pmrecv.c and pmprobe.c),
there are some memcheck code paths that access status but do not check
for STATUS_IGNORE, please review them.
$ cat tmp.c
#include
int main(int argc, char *argv
George,
As I wrote in the ticket a few minutes ago, your patch looks good and
it passed my test. My previous patch didn't care about generalized
requests so your patch is better.
Thanks,
Takahiro Kawashima,
from my home
> Takahiro,
>
> I went over this ticket and attached a new patch. Basically
Right you are -- many thanks for finding the issue. I just committed a fix to
the trunk in SVN r28430; I'll CMR it over to v1.7.
On May 1, 2013, at 4:56 AM, Lisandro Dalcin wrote:
> It seems that Mrecv() tries to write on the status arg, even when it
> is STATUS_IGNORE. Looking at the sources
*&&*$# . Can someone undo this.
-Nathan
On Wed, May 01, 2013 at 12:01:48PM -0400, svn-commit-mai...@open-mpi.org wrote:
> Author: hjelmn (Nathan Hjelm)
> Date: 2013-05-01 12:01:48 EDT (Wed, 01 May 2013)
> New Revision: 28435
> URL: https://svn.open-mpi.org/trac/ompi/changeset/28435
>
> Log:
> im
Nevermind. Figured it out.
-Nathan
On Wed, May 01, 2013 at 10:06:08AM -0600, Nathan Hjelm wrote:
> *&&*$# . Can someone undo this.
>
> -Nathan
>
> On Wed, May 01, 2013 at 12:01:48PM -0400, svn-commit-mai...@open-mpi.org
> wrote:
> > Author: hjelmn (Nathan Hjelm)
> > Date: 2013-05-01 12:01:48 E
On 04/29/2013 11:04 AM, Ralph Castain wrote:
On Apr 27, 2013, at 7:37 PM, Orion Poplawski wrote:
On 04/26/2013 08:53 PM, Ralph Castain wrote:
On Apr 26, 2013, at 7:40 PM, Orion Poplawski wrote:
So it looks like I will need to shortly be looking at how to link against an
external libeven
On May 1, 2013, at 7:32 PM, Orion Poplawski wrote:
> On 04/29/2013 11:04 AM, Ralph Castain wrote:
>>
>> On Apr 27, 2013, at 7:37 PM, Orion Poplawski wrote:
>>
>>> On 04/26/2013 08:53 PM, Ralph Castain wrote:
On Apr 26, 2013, at 7:40 PM, Orion Poplawski wrote:
>
> So it lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
We're about to bring up a new cluster (IBM iDataplex with SandyBridge
CPUs including 10 nodes with two Intel Xeon Phi cards) and I'm at the
stage where we need to pick an OMPI release to put on.
Given that this system is at the start of its
