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 0x00007ffff7a82fc4 in opal_libevent2019_event_priority_set (ev=0x63b100,
pri=3)
at ../../../../../../ompi/opal/mca/event/libevent2019/libevent/event.c:1849
#1 0x00007ffff7a3402e in orte_iof_base_open ()
at ../../../../ompi/orte/mca/iof/base/iof_base_open.c:259
#2 0x00007ffff7a058d4 in orte_info_register_components
(mca_types=0x7fffffffd7b0,
component_map=0x7fffffffd700) at
../../ompi/orte/runtime/orte_info_support.c:199
#3 0x0000000000403572 in main (argc=1, argv=0x7fffffffd998)
at ../../../../ompi/ompi/tools/ompi_info/ompi_info.c:148
george.
On Oct 25, 2012, at 14:23 , Ralph Castain <r...@open-mpi.org> wrote:
> 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
> validate this release!! So please at least ensure it compiles and runs on the
> usual systems.
>
> Thanks
> Ralph
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
