[mpiwg-tools] Intel MPI Backend Breakpoint
dmitry.durnov at intel.com
Wed Jul 12 13:44:20 CDT 2017
I've started a separate mail thread where we may discuss details.
From: mpiwg-tools [mailto:mpiwg-tools-bounces at lists.mpi-forum.org] On Behalf Of Alexander Zahdeh
Sent: Wednesday, July 12, 2017 7:27 PM
To: mpiwg-tools at lists.mpi-forum.org
Subject: [mpiwg-tools] Intel MPI Backend Breakpoint
This is Alex Zahdeh, one of the debugger tools developers at Cray. I had a question about how Intel MPI handles synchronization according to the MPIR debugging standard. The usual procedure for our debugger is to launch tool daemons to attach to the backend application processes while the application launcher is held at MPIR_Breakpoint. At this point the application process must be in some sort of barrier so the debugger tries to return the user to their own code by setting breakpoints at various initialization symbols for different parallel models, continuing, hitting one of the breakpoints, deleting the rest and finishing the current function. This works if the application is held before the breakpoints we set which does not seem to be the case with Intel MPI. Is there a more standard approach to returning the user to their own code or does it vary by programming model and implementor? And specifically with Intel MPI would there be a good breakpoint to set in this scenario?
Alex Zahdeh | PE Debugger Development | Cray Inc.
azahdeh at cray.com | Office: 651-967-9628 | Cell: 651-300-2005 _______________________________________________
mpiwg-tools mailing list
mpiwg-tools at lists.mpi-forum.org
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
More information about the mpiwg-tools