Hi,
what were we talking about again ;-)?
Aah, right: 1.3.2 is out the door, the dust has settled.
Tuesday, next week, I'd like to apply the patch (produced by
contrib/check_unnecessary_headers.sh, see the first email).
This will require just two patches:
- one (independent patch) for a few min
Hi,
I'm currently looking at this bug:
http://www.open-mpi.org/community/lists/users/2008/12/7611.php
I'm using the 1.3.2 tarball.
Valgrind tells me that there is an invalid write (of size 1) in
osc_pt2pt_data_move.c at line 229 which is the
statement
memcpy((unsigned char*) buffer->payl
Done; thanks!
https://svn.open-mpi.org/trac/ompi/changeset/21060
(I added in a few more memset's and calloc's elsewhere in if.c, just
to be complete)
On Apr 23, 2009, at 11:36 AM, Number Cruncher wrote:
Although --enable-mem-debug resolves the issue, I get warnings about
uninitializ
Although --enable-mem-debug resolves the issue, I get warnings about
uninitialized bytes in writev from the opal_if_t structs in opal_ifinit:
==25777== Syscall param writev(vector[...]) points to uninitialised byte(s)
==25777==at 0x34DE2C9F0C: writev (in /lib64/libc-2.6.so)
==25777==by 0
Blah! Wrong "devel" list -- sorry folks!
On Apr 23, 2009, at 10:33 AM, Jeff Squyres (jsquyres) wrote:
Ok, I opened a Google account with the name "openmpi" this morning,
and using Ethan's cell phone (heh; turns out that I had already used
mine), we verified it for use with GAE. Woo hoo!
"ope
Ok, I opened a Google account with the name "openmpi" this morning,
and using Ethan's cell phone (heh; turns out that I had already used
mine), we verified it for use with GAE. Woo hoo!
"open-mpi-mtt" is the name of the Google Apps application.
I'll send the relevant authentication informat
