Logic program diagnosis from specifications:
Abstract: "This paper presents a framework for locating bugs of Prolog programs from specifications. To be debugged, each predicate is specified by a set of universal formulas either of the form [formula] or of the form [formula]. The system generates each test case by executing the antecedant...
Gespeichert in:
| Format: | Buch |
|---|---|
| Sprache: | English |
| Veröffentlicht: |
Tokyo, Japan
1989
|
| Schriftenreihe: | Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report
447 |
| Schlagworte: | |
| Zusammenfassung: | Abstract: "This paper presents a framework for locating bugs of Prolog programs from specifications. To be debugged, each predicate is specified by a set of universal formulas either of the form [formula] or of the form [formula]. The system generates each test case by executing the antecedant [sic] part of such a formula and checks the test case by executing the consequence part under the answer substitution just obtained. If the latter execution cannot succeed without instantiating the variables, it turns out that either the execution of atom A (in the consequence part) under the answer substitution has failed unexpectedly, or the execution of atom A (in the antecedant [sic] part) under the answer substitution has succeeded unexpectedly Then, the system locates the bug using the specifications by checking whether each subcomputation has proceeded as intended while tracing the execution of the atom in a top-down manner. Our approach is a generalization of both the bug location algorithm in Shapiro's 'Algorithmic Debugging' and that in Dershowitz-Lee's 'Deductive Debugging.' The relation between the generation of test cases and the verification of logic programs is discussed as well. |
| Beschreibung: | 40 S. |
Internformat
MARC
| LEADER | 00000nam a2200000 cb4500 | ||
|---|---|---|---|
| 001 | BV010946998 | ||
| 003 | DE-604 | ||
| 005 | 00000000000000.0 | ||
| 007 | t | ||
| 008 | 960912s1989 |||| 00||| engod | ||
| 035 | |a (OCoLC)22643011 | ||
| 035 | |a (DE-599)BVBBV010946998 | ||
| 040 | |a DE-604 |b ger |e rakddb | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-91G | ||
| 245 | 1 | 0 | |a Logic program diagnosis from specifications |c by T. Kanamori ... |
| 264 | 1 | |a Tokyo, Japan |c 1989 | |
| 300 | |a 40 S. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 490 | 1 | |a Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report |v 447 | |
| 520 | 3 | |a Abstract: "This paper presents a framework for locating bugs of Prolog programs from specifications. To be debugged, each predicate is specified by a set of universal formulas either of the form [formula] or of the form [formula]. The system generates each test case by executing the antecedant [sic] part of such a formula and checks the test case by executing the consequence part under the answer substitution just obtained. If the latter execution cannot succeed without instantiating the variables, it turns out that either the execution of atom A (in the consequence part) under the answer substitution has failed unexpectedly, or the execution of atom A (in the antecedant [sic] part) under the answer substitution has succeeded unexpectedly | |
| 520 | 3 | |a Then, the system locates the bug using the specifications by checking whether each subcomputation has proceeded as intended while tracing the execution of the atom in a top-down manner. Our approach is a generalization of both the bug location algorithm in Shapiro's 'Algorithmic Debugging' and that in Dershowitz-Lee's 'Deductive Debugging.' The relation between the generation of test cases and the verification of logic programs is discussed as well. | |
| 650 | 4 | |a Debugging in computer science | |
| 650 | 4 | |a Prolog (Computer program language) | |
| 700 | 1 | |a Kanamori, Tadashi |e Sonstige |4 oth | |
| 830 | 0 | |a Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report |v 447 |w (DE-604)BV010923438 |9 447 | |
| 999 | |a oai:aleph.bib-bvb.de:BVB01-007321234 | ||
Datensatz im Suchindex
| _version_ | 1804125433600409600 |
|---|---|
| any_adam_object | |
| building | Verbundindex |
| bvnumber | BV010946998 |
| ctrlnum | (OCoLC)22643011 (DE-599)BVBBV010946998 |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02199nam a2200313 cb4500</leader><controlfield tag="001">BV010946998</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">00000000000000.0</controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">960912s1989 |||| 00||| engod</controlfield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)22643011</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV010946998</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rakddb</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91G</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Logic program diagnosis from specifications</subfield><subfield code="c">by T. Kanamori ...</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Tokyo, Japan</subfield><subfield code="c">1989</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">40 S.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="1" ind2=" "><subfield code="a">Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report</subfield><subfield code="v">447</subfield></datafield><datafield tag="520" ind1="3" ind2=" "><subfield code="a">Abstract: "This paper presents a framework for locating bugs of Prolog programs from specifications. To be debugged, each predicate is specified by a set of universal formulas either of the form [formula] or of the form [formula]. The system generates each test case by executing the antecedant [sic] part of such a formula and checks the test case by executing the consequence part under the answer substitution just obtained. If the latter execution cannot succeed without instantiating the variables, it turns out that either the execution of atom A (in the consequence part) under the answer substitution has failed unexpectedly, or the execution of atom A (in the antecedant [sic] part) under the answer substitution has succeeded unexpectedly</subfield></datafield><datafield tag="520" ind1="3" ind2=" "><subfield code="a">Then, the system locates the bug using the specifications by checking whether each subcomputation has proceeded as intended while tracing the execution of the atom in a top-down manner. Our approach is a generalization of both the bug location algorithm in Shapiro's 'Algorithmic Debugging' and that in Dershowitz-Lee's 'Deductive Debugging.' The relation between the generation of test cases and the verification of logic programs is discussed as well.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Debugging in computer science</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Prolog (Computer program language)</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Kanamori, Tadashi</subfield><subfield code="e">Sonstige</subfield><subfield code="4">oth</subfield></datafield><datafield tag="830" ind1=" " ind2="0"><subfield code="a">Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report</subfield><subfield code="v">447</subfield><subfield code="w">(DE-604)BV010923438</subfield><subfield code="9">447</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-007321234</subfield></datafield></record></collection> |
| id | DE-604.BV010946998 |
| illustrated | Not Illustrated |
| indexdate | 2024-07-09T18:01:29Z |
| institution | BVB |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-007321234 |
| oclc_num | 22643011 |
| open_access_boolean | |
| owner | DE-91G DE-BY-TUM |
| owner_facet | DE-91G DE-BY-TUM |
| physical | 40 S. |
| publishDate | 1989 |
| publishDateSearch | 1989 |
| publishDateSort | 1989 |
| record_format | marc |
| series | Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report |
| series2 | Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report |
| spelling | Logic program diagnosis from specifications by T. Kanamori ... Tokyo, Japan 1989 40 S. txt rdacontent n rdamedia nc rdacarrier Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report 447 Abstract: "This paper presents a framework for locating bugs of Prolog programs from specifications. To be debugged, each predicate is specified by a set of universal formulas either of the form [formula] or of the form [formula]. The system generates each test case by executing the antecedant [sic] part of such a formula and checks the test case by executing the consequence part under the answer substitution just obtained. If the latter execution cannot succeed without instantiating the variables, it turns out that either the execution of atom A (in the consequence part) under the answer substitution has failed unexpectedly, or the execution of atom A (in the antecedant [sic] part) under the answer substitution has succeeded unexpectedly Then, the system locates the bug using the specifications by checking whether each subcomputation has proceeded as intended while tracing the execution of the atom in a top-down manner. Our approach is a generalization of both the bug location algorithm in Shapiro's 'Algorithmic Debugging' and that in Dershowitz-Lee's 'Deductive Debugging.' The relation between the generation of test cases and the verification of logic programs is discussed as well. Debugging in computer science Prolog (Computer program language) Kanamori, Tadashi Sonstige oth Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report 447 (DE-604)BV010923438 447 |
| spellingShingle | Logic program diagnosis from specifications Shin-Sedai-Konpyūta-Gijutsu-Kaihatsu-Kikō <Tōkyō>: ICOT technical report Debugging in computer science Prolog (Computer program language) |
| title | Logic program diagnosis from specifications |
| title_auth | Logic program diagnosis from specifications |
| title_exact_search | Logic program diagnosis from specifications |
| title_full | Logic program diagnosis from specifications by T. Kanamori ... |
| title_fullStr | Logic program diagnosis from specifications by T. Kanamori ... |
| title_full_unstemmed | Logic program diagnosis from specifications by T. Kanamori ... |
| title_short | Logic program diagnosis from specifications |
| title_sort | logic program diagnosis from specifications |
| topic | Debugging in computer science Prolog (Computer program language) |
| topic_facet | Debugging in computer science Prolog (Computer program language) |
| volume_link | (DE-604)BV010923438 |
| work_keys_str_mv | AT kanamoritadashi logicprogramdiagnosisfromspecifications |