Yes - we were having problems making symbols in orterun visible for the "stat" debugger when built dynamically. The symbols are actually instantiated in the debugger base, but they need to be "seen" in orterun prior to us calling orte_init. So, we had to explicitly reference them.
It was working just fine, and was tested against stat, totalview, and pdb at the time. Not sure why it is now causing problems. However, as I told Nathan, if we find everything works okay without the line, then by all means remove it. However, be sure we check "stat", and that we check both static and dynamic builds under Linux as well as the Cray (IIRC, Nathan is working on the Cray with a static build?). On Dec 14, 2011, at 6:24 PM, Jeff Squyres wrote: > Looks like that line came over in > https://svn.open-mpi.org/trac/ompi/changeset/24561, which was bringing over > the debugger ORTE framework from the trunk > (https://svn.open-mpi.org/trac/ompi/ticket/2688). > > Ralph -- do you remember why that line is there? > > > On Dec 14, 2011, at 7:21 PM, Nathan Hjelm wrote: > >> There still seems to be an issue with using mpirun --debug with totalview. >> For some reason totalview is not breaking on MPIR_Breakpoint. Removing the >> foo = MPIR_Breakpoint line from orterun.c fixes this issue. >> >> Is there any reason I shouldn't remove that line? Any other debuggers that >> might break? >> >> -Nathan >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
