DynamoRIO / DynamoRIO/dynamorio
ASSERT skip_pc != NULL && cti_pc != NULL in signal.1011 test on AArch64
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 629
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 30
Description
This happened once:
http://jenkins.dynamorio.org:8080/job/DynamoRIO-AArch64-Precommit/402/
```
debug-internal-64: 163 tests passed, **** 2 tests failed, of which 1 were flaky: ****
code_api|linux.signal1011 => Application /data/jenkins_root/workspace/DynamoRIO-AArch64-Precommit/build/build_debug-internal-64/suite/tests/bin/linux.signal1011 (13008). Internal Error: DynamoRIO debug check failure: /data/jenkins_root/workspace/DynamoRIO-AArch64-Precommit/core/arch/mangle_shared.c:765 skip_pc != NULL cti_pc != NULL
```
Contributor guide
Research direction
Start with the AArch64 Jenkins run linked in the issue and the linux.signal1011 test. Read the assertion at core/arch/mangle_shared.c:765, then investigate why skip_pc and cti_pc can both be null in that test. Done means reproducing or explaining the intermittent failure and making the test pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100