Welcome back, Peter.  :-)

On Mar 21, 2011, at 2:02 PM, Peter Thompson wrote:

> Gee,  I had tried posting that info earlier today, but my post was rejected 
> because my email address has changed.  This is as much a test of that address 
> change request as it is a confirmation of the info Dave reports.  (Of course 
> I'm the one who sent them the info, so it's only a little self-serving ;-)
> 
> Cheers,
> Peter Thompson
> 
> 
> Ralph Castain wrote:
>> Ick - appears that got dropped a long time ago. I'll add it back in and post 
>> a CMR for 1.4 and 1.5 series.
>> 
>> Thanks!
>> Ralph
>> 
>> 
>> On Mar 21, 2011, at 11:08 AM, David Turner wrote:
>> 
>>  
>>> Hi,
>>> 
>>> About a month ago, this topic was discussed with no real resolution:
>>> 
>>> http://www.open-mpi.org/community/lists/users/2011/02/15538.php
>>> 
>>> We noticed the same problem (TV does not display the user's MAIN
>>> routine upon initial startup), and contacted the TV developers.
>>> They suggested a simple OMPI code modification, which we implemented
>>> and tested; it seems to work fine.  Hopefully, this capability
>>> can be restored in future releases.
>>> 
>>> Here is the body of our communication with the TV developers:
>>> 
>>> ----------------------------------------------------------------------
>>> 
>>> Interestingly enough, someone else asked this very same question recently 
>>> and I finally dug into it last week and figured out what was going on. 
>>> TotalView publishes a public interface which allows any MPI implementor to 
>>> set things up so that it should work fairly seamless with TotalView. I 
>>> found that one of the defines in the interface is
>>> 
>>> MPIR_force_to_main
>>> 
>>> and when we find this symbol defined in mpirun (or orterun in Open MPI's 
>>> case) then we spend a bit more effort to focus the source pane on the main 
>>> routine. As you may guess, this is NOT being defined in OpenMPI 1.4.2. It 
>>> was being defined in the 1.2.x builds though, in a routine called 
>>> totalview.c. OpenMPI has been re-worked significantly since then, and 
>>> totalview.c has been replaced by debuggers.c in orte/tools/orterun. About 
>>> line 130 to 140 (depending on any changes since my look at the 1.4.1 
>>> sources) you should find a number of MPIR_ symbols being defined.
>>> 
>>> struct MPIR_PROCDESC *MPIR_proctable = NULL;
>>> int MPIR_proctable_size = 0;
>>> int MPIR_being_debugged = 0;
>>> volatile int MPIR_debug_state = 0;
>>> volatile int MPIR_i_am_starter = 0;
>>> volatile int MPIR_partial_attach_ok = 1;
>>> 
>>> 
>>> I believe you should be able to insert the line:
>>> 
>>> int MPIR_force_to_main = 0;
>>> 
>>> into this section, and then the behavior you are looking for should work 
>>> after you rebuild OpenMPI. I haven't yet had the time to do that myself, 
>>> but that was all that existed in the 1.2.x sources, and I know those 
>>> achieved the desired effect. It's quite possible that someone realized the 
>>> symbol was initialized, but wasn't be used anyplace, so they just removed 
>>> it. Without realizing we were looking for it in the debugger. When I 
>>> pointed this out to the other user, he said he would try it out and pass it 
>>> on to the Open MPI group. I just checked on that thread, and didn't see any 
>>> update, so I passed on the info myself.
>>> 
>>> ----------------------------------------------------------------------
>>> 
>>> -- 
>>> Best regards,
>>> 
>>> David Turner
>>> User Services Group        email: dptur...@lbl.gov
>>> NERSC Division             phone: (510) 486-4027
>>> Lawrence Berkeley Lab        fax: (510) 486-4316
>>> _______________________________________________
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>    
>> 
>> 
>> _______________________________________________
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>  
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/


Reply via email to