[OMPI devel] segv in ompi_info
$/usr/mpi/gcc/openmpi-1.8.2a1/bin/ompi_info -a -l 9|less Caught signal 13 (Broken pipe) backtrace 2 0x00054cac mxm_handle_error() /var/tmp/OFED_topdir/BUILD/mxm-3.2.2883/src/mxm/util/debug/debug.c:653 3 0x00054e74 mxm_error_signal_handler() /var/tmp/OFED_topdir/BUILD/mxm-3.2.2883/src/mxm/util/debug/debug.c:628 4 0x0033fbe32920 killpg() ??:0 5 0x0033fbedb650 __write_nocancel() interp.c:0 6 0x0033fbe71d53 _IO_file_write@@GLIBC_2.2.5() ??:0 7 0x0033fbe73305 _IO_do_write@@GLIBC_2.2.5() ??:0 8 0x0033fbe719cd _IO_file_xsputn@@GLIBC_2.2.5() ??:0 9 0x0033fbe48410 _IO_vfprintf() ??:0 10 0x0033fbe4f40a printf() ??:0 11 0x0002bc84 opal_info_out() /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:853 12 0x0002c6bb opal_info_show_mca_group_params() /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:658 13 0x0002c882 opal_info_show_mca_group_params() /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:716 14 0x0002cc13 opal_info_show_mca_params() /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:742 15 0x0002d074 opal_info_do_params() /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:485 16 0x0040167b main() ??:0 17 0x0033fbe1ecdd __libc_start_main() ??:0 18 0x00401349 _start() ??:0 ===
Re: [OMPI devel] segv in ompi_info
I'm unable to replicate. Please provide more detail...? Is this a problem in the MXM component? On Jul 8, 2014, at 9:20 AM, Mike Dubman wrote: > > > $/usr/mpi/gcc/openmpi-1.8.2a1/bin/ompi_info -a -l 9|less > Caught signal 13 (Broken pipe) > backtrace > 2 0x00054cac mxm_handle_error() > /var/tmp/OFED_topdir/BUILD/mxm-3.2.2883/src/mxm/util/debug/debug.c:653 > 3 0x00054e74 mxm_error_signal_handler() > /var/tmp/OFED_topdir/BUILD/mxm-3.2.2883/src/mxm/util/debug/debug.c:628 > 4 0x0033fbe32920 killpg() ??:0 > 5 0x0033fbedb650 __write_nocancel() interp.c:0 > 6 0x0033fbe71d53 _IO_file_write@@GLIBC_2.2.5() ??:0 > 7 0x0033fbe73305 _IO_do_write@@GLIBC_2.2.5() ??:0 > 8 0x0033fbe719cd _IO_file_xsputn@@GLIBC_2.2.5() ??:0 > 9 0x0033fbe48410 _IO_vfprintf() ??:0 > 10 0x0033fbe4f40a printf() ??:0 > 11 0x0002bc84 opal_info_out() > /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:853 > 12 0x0002c6bb opal_info_show_mca_group_params() > /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:658 > 13 0x0002c882 opal_info_show_mca_group_params() > /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:716 > 14 0x0002cc13 opal_info_show_mca_params() > /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:742 > 15 0x0002d074 opal_info_do_params() > /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2a1/opal/runtime/opal_info_support.c:485 > 16 0x0040167b main() ??:0 > 17 0x0033fbe1ecdd __libc_start_main() ??:0 > 18 0x00401349 _start() ??:0 > === > ___ > 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/2014/07/15075.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] OMPI BTL async progress prototype discussion meeting
I got a lot of random calendar "accept" responses (i.e., "random" = "from people I don't know"). I was a little surprised; I had expected only core Open MPI developers to respond -- I sent it to the devel list (vs. sending to a specific list of people) purely out of laziness/convenience. You're all free to attend, but just to be clear: this meeting is not intended to be an Open MPI presentation to the world. We will not be providing Open MPI Internals 101 during this meeting, for example. It is assumed that participants will be deeply familiar with Open MPI internals. On Jun 26, 2014, at 11:40 AM, Jeff Squyres (jsquyres) wrote: > When: Wednesday, July 23, 2014 2:00 PM-3:00 PM. (UTC-05:00) Eastern Time (US > & Canada) > Where: Webex > > *~*~*~*~*~*~*~*~*~* > > LANL and UTK are going to prototype the proposed asynchronous progress > approach in sm, ugni, and openib BTLs. This meeting is to discuss their > progress, with special attention given to ensuring that performance is > maintained from the current non-asynchronous approach. > > -- > > You can forward this email invitation to attendees > > Hello , > > Jeff Squyres invites you to attend this online meeting. > > Topic: OMPI asynch progress discussion -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
[OMPI devel] Shared library version numbers for 1.8.2
Here's what I think VERSION should be for 1.8.2: https://svn.open-mpi.org/trac/ompi/changeset/32165 I left comments in the VERSION file as to why I think each version number should change. Can someone please verify that this work is correct? If so, we can remove the comments (before the final 1.8.2 release). -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
