trailofbits / trailofbits/ruzzy
Harness ends with DEADLYSIGNAL at start
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 120
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Often running a harness ends with:
AddressSanitizer: DEADLYSIGNAL
AddressSanitizer: DEADLYSIGNAL
AddressSanitizer: DEADLYSIGNAL
...
AddressSanitizer: DEADLYSIGNAL
AddressSanitizer: DEADLYSIGNAL
AddressSanitizer: DEADLYSIGNAL
In my experience, it always happens at the very beginning of running the harness.
While my setup is quite specific, I believe @mschwager observed the same behavior. (Am I right?)
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 by reproducing the failure at the beginning of the harness run and capture the full AddressSanitizer output. Compare the reported behavior with the setup described in the issue and determine a clear cause and reproducible fix; done means the harness no longer ends with repeated DEADLYSIGNAL messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100