Improved interpreter error messages for quicker error identification

Open
#4,670 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, shell
Domain
compilers, developer-experience

Research direction

Start with the krun command and the K tools documentation linked in the issue; inspect how the interpreter reports temporary input and result.kore paths. Done means errors provide enough rewrite-progress and stored Kore information to identify failures without rerunning the full depth run.

Written by the indexing model from the issue text.

Description

enhancement llvm-backend
  • When the interpreter takes a long time without producing results, I’m unsure where it is in the rewrite process and if there are any issues. Plus, after an error, I have to rerun everything from the beginning. I wrote a script to execute 1000 depth runs continuously to quickly identify problems.
  • Regarding error messages like these, there’s no default saving of temporary files, so I have to rerun to find out. The stored information is in Kore, which needs to be pretty-printed to understand its meaning better. It would be great if it could be directly bound to the error messages. I feel that most issues arise from Map-related problems and incomplete coverage of conditions in function rules.
[Error] krun: .build/ukm-testing-kompiled/interpreter 
/tmp/.krun-2024-10-11-23-11-32-E5cpgVDb9R/tmp.in.RcBlduf0fG 700 
/tmp/.krun-2024-10-11-23-11-32-E5cpgVDb9R/result.kore

Debugging might be quite complex and may not allow for quick error tracking.
information: https://kframework.org/docs/ktools/"

Dominant language
Python
Stars
591
Forks
163
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from runtimeverification/k

All issues in runtimeverification/k

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.