dc.contributor | Universidad EAFIT. Departamento de Ciencias | |
dc.contributor | Lógica y Computación | |
dc.creator | Alpuente, M. | |
dc.creator | Ballis, D. | |
dc.creator | Correa, F. | |
dc.creator | Falaschi, M. | |
dc.creator | Alpuente, M. | |
dc.creator | Ballis, D. | |
dc.creator | Correa, F. | |
dc.creator | Falaschi, M. | |
dc.date.accessioned | 2021-03-26T21:32:04Z | |
dc.date.accessioned | 2022-09-23T20:29:47Z | |
dc.date.available | 2021-03-26T21:32:04Z | |
dc.date.available | 2022-09-23T20:29:47Z | |
dc.date.created | 2021-03-26T21:32:04Z | |
dc.date.issued | 2010-10-29 | |
dc.identifier | 03043975 | |
dc.identifier | 18792294 | |
dc.identifier | WOS;000283695700002 | |
dc.identifier | SCOPUS;2-s2.0-77957819191 | |
dc.identifier | http://hdl.handle.net/10784/27338 | |
dc.identifier | 10.1016/j.tcs.2010.07.009 | |
dc.identifier.uri | http://repositorioslatinoamericanos.uchile.cl/handle/2250/3515121 | |
dc.description.abstract | We present a generic scheme for the declarative debugging of programs that are written in rewriting-based languages that are equipped with narrowing. Our aim is to provide an integrated development environment in which it is possible to debug a program and then correct it automatically. Our methodology is based on the combination (in a single framework) of a semantics-based diagnoser that identifies those parts of the code that contain errors and an inductive learner that tries to repair them, once the bugs have been located in the program. We develop our methodology in several steps. First, we associate with our programs a semantics that is based on a (continuous) immediate consequence operator, TR, which models the answers computed by narrowing and is parametric w.r.t. the evaluation strategy, which can be eager or lazy. Then, we show that, given the intended specification of a program R, it is possible to check the correctness of R by a single step of TR. In order to develop an effective debugging method, we approximate the computed answers semantics of R and derive a finitely terminating bottom-up abstract diagnosis method, which can be used statically. Finally, a bug-correction program synthesis methodology attempts to correct the erroneous components of the wrong code. We propose a hybrid, top-down (unfolding-based) as well as bottom-up (induction-based), correction approach that is driven by a set of evidence examples which are automatically produced as an outcome by the diagnoser. The resulting program is proven to be correct and complete w.r.t. the considered example sets. Our debugging framework does not require the user to provide error symptoms in advance or to answer difficult questions concerning program correctness. An implementation of our debugging system has been undertaken which demonstrates the workability of our approach. © 2010 Elsevier B.V. All rights reserved. | |
dc.publisher | ELSEVIER SCIENCE BV | |
dc.relation | https://www.scopus.com/inward/record.uri?eid=2-s2.0-77957819191&doi=10.1016%2fj.tcs.2010.07.009&partnerID=40&md5=e9d61f5c82a2bbc84bdb7c41e12fe092 | |
dc.rights | https://v2.sherpa.ac.uk/id/publication/issn/0304-3975 | |
dc.source | THEORETICAL COMPUTER SCIENCE | |
dc.subject | Debugging | |
dc.subject | Debugging methods | |
dc.subject | Debugging systems | |
dc.subject | Declarative debugging | |
dc.subject | Diagnosis methods | |
dc.subject | Evaluation strategies | |
dc.subject | Functional logic programming | |
dc.subject | Integrated development environment | |
dc.subject | Integrated frameworks | |
dc.subject | Narrowing | |
dc.subject | Program correctness | |
dc.subject | Program synthesis | |
dc.subject | Program transformations | |
dc.subject | Rule based | |
dc.subject | Single-step | |
dc.subject | Topdown | |
dc.subject | Functional programming | |
dc.subject | Logic programming | |
dc.subject | Program debugging | |
dc.subject | Web services | |
dc.subject | Program diagnostics | |
dc.title | An integrated framework for the diagnosis and correction of rule-based programs | |
dc.type | article | |
dc.type | info:eu-repo/semantics/article | |
dc.type | info:eu-repo/semantics/publishedVersion | |
dc.type | publishedVersion | |