BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20230124T171523Z
LOCATION:C143-149
DTSTART;TZID=America/Chicago:20221114T104500
DTEND;TZID=America/Chicago:20221114T110500
UID:submissions.supercomputing.org_SC22_sess439_ws_scsc112@linklings.com
SUMMARY:Debugging MPI Implementations via Reduction-to-Primitives
DESCRIPTION:Workshop\n\nDebugging MPI Implementations via Reduction-to-Pri
 mitives\n\nCooperman, Li, Zhao\n\nTesting correctness of either a new MPI 
 implementation or a transparent checkpointing package for MPI is inherentl
 y difficult.  A bug is often observed when running a correctly written MPI
  application, and it produces an error.  Tracing the bug to a particular s
 ubsystem of the MPI package is difficult due to issues of complex parallel
 ism, race conditions, etc.  This work provides tools to decide if the bug 
 is: in the subsystem implementing of collective communication; or in the s
 ubsystem implementing point-to-point communication; or in some other subsy
 stem.  The tools were produced in the context of testing a new system, MAN
 A.  MANA is not a standalone MPI implementation, but rather a package for 
 transparent checkpointing of MPI applications.  In addition, a short surve
 y of other debugging tools for MPI is presented.  The strategy of transfor
 ming the execution for purposes of diagnosing a bug appears to be distinct
  from most existing debugging approaches.\n\nSession Format: Recorded\n\nT
 ag: Reliability and Resiliency\n\nRegistration Category: Workshop Reg Pass
END:VEVENT
END:VCALENDAR