Non-interrupting debug info from Ctrl-C
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
Currently the interrupt signal gives four options:
```m2
Exit (y=yes/n=no/a=abort/b=backtrace)?
```
Would be nice if there was a a way to get some debug info from this without quitting or aborting.
For instance:
- the current location of the interpreter in the top-level to see where is the hold-up
- a table of active threads and same info for each (could be combined to include main thread)
- if possible, current location in the engine/libraries
- time elapsed since last command or current memory usage
Even better would be the option to delegate the current computation to a thread without aborting it and switch to the interpreter on a free thread (I think I've mentioned this before).
We could have a separate signal for this, e.g. USR1, but Ctrl-C is easier to signal.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; begin by locating the Ctrl-C interrupt handling and the interpreter's thread or execution entry points. Define which non-interrupting debug information is feasible and how completion would be verified without aborting the current computation.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100