Hi! I am quite familiar with the declarative debugging approach to locate the mistake when the program is too specific. But I haven’t found any more deatailed materials about how to approach the situation, when the program is too general. Usually I came across this situation when the mistake is hi…

What is the declarative testing/debugging way that you refer to? Altogether using constraints opens up your program to a completely new class of problems.

I’m sorry, I didn’t realise that this my statement is pretty vague. It is based on Markus Triska’s chapters for declarative debugging and declarative testing , as well as a lot of false’s stackowerflow posts about this, and some others as well. It’s just about not using the trace right away (or at …

Those chapters are pretty slim. I almost get the feeling that the author might have hand-picked the examples to prove their point. Failure slice, as presented by the user false on SO, is, at its core, “a concrete program-slicing technique.” (this quote is straight from the tag description on SO ). H…

[image] mjano314: I haven’t found any more deatailed materials about how to approach the situation See: [image] 'failure-slice' tag wiki Stack Overflow | The World’s Largest Online Community for Developers which leads to the paper “Localizing and exp…

[image] Boris: Those chapters are pretty slim. I agree with this. Hopefully they will be extended one day. False has more posts about declarative debugging (or debugger free debugging as he calls it) on SO. [image] Boris: using CLP(FD) instead of normal arithmetic… I understand your p…

[image] EricGT: which leads to the paper “Localizing and explaining reasons for non-terminating logic programs with failure-slices” ( PDF ) Thanks. I had this one in my to-read list but lost it. But I don’t think this would help in too general programs. Unfortunatelly I don’t remember the re…

There is another method. It is called “reading the code” :slight_smile: I do it regularly, also at work, and with all the languages. Read the code, cross-check it with the specs, and with all the places where this code is used. (In some code bases I have had to work on, tracing can be absurdly diff…

[image] Boris: There is another method. It is called “reading the code” :slight_smile: Aaah, the famous RTFM :slight_smile: In the ideal world where you would have an infinite amount of time and you have a years of experiences to just read the code and see the mistake right away, it would be …

[image] anon95304481: Its called code review. RTFM is something else. I know. There is the group of “just read” solutions. Read the manual, read the code, etc. And probably the most famous abbreviation is RTFM about reading the * manuals, therefore I used it there as a sticker for all the “ju…

Declarative debugging too general programs

Help!

EricGT June 1, 2021, 10:25pm 8

Here is a very loose collection of references related to debugging Prolog code not that it may be of value to your specific problem, it is nice to know for future needs.

Bug hunting toolbox

Topic		Replies	Views
Looking for a study partner for intermediate/advanced prolog (no school level) Looking for Group	14	832	July 30, 2024
Bug hunting toolbox Wiki	3	2986	June 28, 2026
Errors considered harmful Request For Comments	106	5918	August 8, 2021
Fully understanding the "intricacies" of the Prolog code design process Help!	40	664	July 12, 2024
Pure and correct Prolog - what is it? (Creating Prolog Cookbook) Looking for Group	19	2108	January 30, 2020

Declarative debugging too general programs

Related topics