Okay, 1.7.0rc4 has been posted, with ompi_info fixed :-)
On Oct 25, 2012, at 2:47 PM, Ralph Castain wrote:
> Ah, I see the problem - it is localized to ompi_info and due to the fact that
> we aren't setting things up completely in that code (trying to avoid a
> complete start).
>
> FWIW: you
Ah, I see the problem - it is localized to ompi_info and due to the fact that
we aren't setting things up completely in that code (trying to avoid a complete
start).
FWIW: you are most certainly allowed to amend event callbacks in the base open
function.
I'll fix it. Meantime, the branch seems
Strange - okay, will look.
On Oct 25, 2012, at 2:34 PM, George Bosilca wrote:
> Broken enough that even the ompi_info fails. And for a good reason: one is
> not allowed to amend event callbacks in the component base open function.
>
> Here is the stack:
> 0 0x77a82fc4 in opal_libevent
Broken enough that even the ompi_info fails. And for a good reason: one is not
allowed to amend event callbacks in the component base open function.
Here is the stack:
0 0x77a82fc4 in opal_libevent2019_event_priority_set (ev=0x63b100,
pri=3)
at ../../../../../../ompi/opal/mca/event/
Hi folks
We have posted the first release candidate for the 1.7.0 release in the usual
place:
http://www.open-mpi.org/software/ompi/v1.7/
Please put it thru the wringer to help us validate it prior to release later
this month. We are still updating the NEWS section, but we REALLY need to
vali
