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:20211207T055403Z
LOCATION:Second Floor Atrium
DTSTART;TZID=America/Chicago:20211116T083000
DTEND;TZID=America/Chicago:20211116T170000
UID:submissions.supercomputing.org_SC21_sess278_rpost142@linklings.com
SUMMARY:Handling C++ Exceptions in MPI Applications
DESCRIPTION:Posters, Research Posters\n\nHandling C++ Exceptions in MPI Ap
 plications\n\nJaros\n\nHandling error states in C++ applications is manage
 d by exceptions. In distributed applications, it is necessary to inform th
 e other processes, that something wrong happened, and the application shou
 ld either recover from the faulty state, or report the error and terminate
  gracefully. Unfortunately, the MPI standard does not provide any support 
 for distributed error handling.\n\nThis poster presents a new approach for
  exceptions-handling in MPI applications. The goals are: to report any fau
 lty state to the user in a nicely formatted way by just a single rank; to 
 ensure the application will never deadlock; and to propose a simple interf
 ace and ensure interoperability with other C/C++ libraries. The code was t
 ested with several injected errors into multiple ranks such as non-existin
 g input file, disk quota exceeded, wrong rank in the MPI call and standard
  system exceptions. In all situations the code has worked properly.\n\nReg
 istration Category: Tech Program Reg Pass, Exhibit Hall Only
END:VEVENT
END:VCALENDAR