首页> 外文期刊>Concurrency and Computation >Parallel program debugging by specification
【24h】

Parallel program debugging by specification

机译:按规范进行并行程序调试

获取原文
获取原文并翻译 | 示例

摘要

Most message passing parallel programs employ logical process topologies with regular characteristics to support their computation. Since process topologies define the relationship between processes, they present an excellent opportunity for debugging. The primary benefit is that process behaviours can be correlated, allowing expected behaviour to be abstracted and identified, and undesirable behaviour reported. However, topology support is inadequate in most message passing parallel programming environments, including the popular Message Passing Interface (MPI) and the Parallel Virtual Machine (PVM). Programmers are forced to implement topology support themselves, increasing the possibility of introducing errors. This paper proposes a trace- and topology-based approach to parallel program debugging, driven by four distinct types of specifications. Trace specifications allow trace data from a variety of sources and message passing libraries to be interpreted in an abstract manner, and topology specifications address the lack of explicit topology knowledge, whilst also facilitating the construction of user-consistent views of the debugging activity. Loop specifications express topology-consistent patterns of expected trace events, allowing conformance testing of associated trace data, and error specifications specify undesirable event interactions, including mismatched message sizes and mismatched communication pairs. Both loop and error specifications are simplified by having knowledge of the actual topologies being debugged. The proposed debugging framework enables a wealth of potential debugging views and techniques.
机译:大多数消息传递并行程序采用具有常规特性的逻辑过程拓扑来支持其计算。由于流程拓扑定义了流程之间的关系,因此它们为调试提供了绝佳的机会。主要好处是可以将过程行为关联起来,从而可以抽象和识别预期的行为,并报告不期望的行为。但是,在大多数消息传递并行编程环境中,包括流行的消息传递接口(MPI)和并行虚拟机(PVM),拓扑支持不足。程序员被迫自己实现拓扑支持,从而增加了引入错误的可能性。本文提出了一种基于跟踪和拓扑的并行程序调试方法,该方法由四种不同类型的规范驱动。跟踪规范允许以抽象的方式解释来自各种来源和消息传递库的跟踪数据,并且拓扑规范解决了缺乏明确的拓扑知识的问题,同时还便于构建用户一致的调试活动视图。循环规范表示预期的跟踪事件的拓扑一致性模式,从而允许对关联的跟踪数据进行一致性测试,而错误规范则指定了不良的事件交互,包括不匹配的消息大小和不匹配的通信对。通过了解要调试的实际拓扑,可以简化循环和错误规范。所提出的调试框架使大量潜在的调试视图和技术成为可能。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号