SBCL keeps on keepin' on even when it should abort
Nobody has claimed this yet.
- Dominant language
- Common Lisp
- Stars
- 1
- Forks
- 1
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
I was running an application with libquil embedded, sent a SIGTERM, and got a long error message that included this:
CORRUPTION WARNING in SBCL pid 52443 pthread 0x16f793000:
Memory fault at 0x5389af61046622df (pc=0x183aab7cc)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
That's absolutely not desirable. It appears that "continuing with fingers crossed" is some kind of optional behavior; we should disable it.
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
Start with the linked SBCL src/runtime/interr.c code and trace how the SIGTERM-triggered corruption warning reaches the “Continuing with fingers crossed” behavior. Confirm how libquil invokes SBCL, then verify that the application aborts instead of continuing after SIGTERM; add or run a focused regression check if the repository provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100