Is it possible to run-time detect this situation? E.g., probe the signal handler, or somesuch.
Rationale: I'd rather have something run-time disabled than not built. Would dlopen'ing libinfinipath change actually change its signal handler behavior? > On Aug 25, 2015, at 4:27 AM, Gilles Gouaillardet <gil...@rist.or.jp> wrote: > > Folks, > > some time ago, some crashes were reported when using java bindings. > one of them was caused was caused by mca_mtl_psm.so. > the root cause is libinfinipath.so initializer sets its own signal handler, > which > conflicts with the signal handler sets by the jvm. > the only workaround is to disable the psm mtl > (e.g. mpirun --mca mtl ^psm ...) > since mpirun --mca mtl_psm_priority 0 ... does not work > (libinfinipath.so is loaded, so the initializer is ran and the signal > handlers are set) > so the psm mtl cannot be disabled by the Java MPI_Init() > > one option is to document this > an other option is not to build the psm mtl if java bindings are built > and an other option is to revamp mca_mtl_psm.so so it does not link with > libinfinipath.so > (use an intermediate component, or dlopen libinfinipath) > > any thoughts ? > > Cheers, > > Gilles > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/08/17838.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
