The Open MPI Team, representing a consortium of research, academic, and
industry partners is just about to release Open MPI version 1.4 in reaction to
the GNU Libtool 2.2.6b security update release (see
http://security-tracker.debian.org/tracker/CVE-2009-3736 for more details).
This mail contai
...and cmr to v1.5. ;-)
(see https://svn.open-mpi.org/trac/ompi/ticket/2133)
On Dec 8, 2009, at 12:33 PM, George Bosilca wrote:
> Rainer,
>
> The patch looks correct. Please feel free to push it in the trunk.
>
> Thanks,
>george.
>
> On Dec 7, 2009, at 11:27 , Rainer Keller wrote:
>
Both of these types (mca_pml_endpoint_t and mca_pml_base_endpoint_t) are
meaningless, they can safely be replaced by void*. We have them clearly typed
(but with just for the sake of understanding, so one can easily figure out what
is supposed to be stored in this specific field. As such, we c
Rainer,
The patch looks correct. Please feel free to push it in the trunk.
Thanks,
george.
On Dec 7, 2009, at 11:27 , Rainer Keller wrote:
> Hello Sylvain,
>
> On Friday 04 December 2009 02:27:22 pm Sylvain Jeaugey wrote:
>> There is definetly something wrong in types.
> Yes, the new ids
I have a better solution ;) Implemented in r22277.
george.
On Dec 8, 2009, at 12:17 , Jeff Squyres wrote:
> On Dec 8, 2009, at 12:05 PM, George Bosilca wrote:
>
>> Both of these types (mca_pml_endpoint_t and mca_pml_base_endpoint_t) are
>> meaningless, they can safely be replaced by void*. W
On Dec 8, 2009, at 12:05 PM, George Bosilca wrote:
> Both of these types (mca_pml_endpoint_t and mca_pml_base_endpoint_t) are
> meaningless, they can safely be replaced by void*. We have them clearly typed
> (but with just for the sake of understanding, so one can easily figure out
> what is su
Pasha,
Both of these types (mca_pml_endpoint_t and mca_pml_base_endpoint_t) are
meaningless, they can safely be replaced by void*. We have them clearly typed
(but with just for the sake of understanding, so one can easily figure out what
is supposed to be stored in this specific field. As such,
Ashley Pittman wrote:
On Tue, 2009-12-08 at 07:39 -0500, Terry Dontje wrote:
Ashley Pittman wrote:
I've seen several cases now where people have functional, installed MPI
libraries yet when they've come to use padb they have discovered a build
problem with the Message Queue DLL which pr
On Tue, 2009-12-08 at 07:39 -0500, Terry Dontje wrote:
> Ashley Pittman wrote:
> > I've seen several cases now where people have functional, installed MPI
> > libraries yet when they've come to use padb they have discovered a build
> > problem with the Message Queue DLL which prevents it from worki
Ashley Pittman wrote:
I've seen several cases now where people have functional, installed MPI
libraries yet when they've come to use padb they have discovered a build
problem with the Message Queue DLL which prevents it from working.
The cases I've seen this happen is with the Sun Studio comp
I've seen several cases now where people have functional, installed MPI
libraries yet when they've come to use padb they have discovered a build
problem with the Message Queue DLL which prevents it from working.
The most common problem is unresolved symbols in the dll meaning the
debugger cannot
Thanks Rainer for the patch. I confirm it solves my testcase as well as
the real application that triggered the bug.
Sylvain
On Mon, 7 Dec 2009, Rainer Keller wrote:
Hello Sylvain,
On Friday 04 December 2009 02:27:22 pm Sylvain Jeaugey wrote:
There is definetly something wrong in types.
Ye
George,
Actually My original question was correct.
In the ompi code base I found ONLY two places where we "use" the structure.
Actually we only assign values for the pointer in DR and CM PML:
ompi/mca/pml/cm/pml_cm.c:145:procs[i]->proc_pml = (struct
mca_pml_base_endpoint_t*) endpoints[i
13 matches
Mail list logo
