On Dec 14, 2011, at 6:44 PM, George Bosilca wrote:
> A comment in the commit suggest that the symbols were not linked into the orterun if they were not accessed there. I guess this was the trick to make sure MPIR_Breakpoint is in there.
> Now that you pointed me to this commit I have to disagree with. Why the MPI debugging symbols have been deleted in favor of using the one on ORTE?
IIRC, there was some issue with getting debuggers attached to running jobs? Been too long. Someone is welcome to play with it again - it was a royal pita to get working. I have no bone in this fight, and no time to go thru that mess again. :-)
> Why the ompi header files contains declarations starting with ORTE_DECLSPEC?
Obviously a typo - should be OMPI_DECLSPEC
> On Dec 14, 2011, at 20:24 , 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?
>>> devel mailing list
>> Jeff Squyres
>> For corporate legal information go to:
>> devel mailing list
> devel mailing list