Cothread builds but fails at runtime on MacOS Arm64 platforms
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- operating-systems
Research direction
Read context/switch-arm64.c and the referenced last commit, then reproduce the failure by running the p4p nose2 tests on GitHub's macos-latest runner. Done means ARM64 works at runtime on modern macOS, or compilation explicitly fails there while remaining functional for platforms such as Raspberry Pi.
Written by the indexing model from the issue text.
Description
Cothread claims to have support for arm64 architecture, denoted by the switch-arm64.c file. However, as noted in the last commit made, it does not actually work at runtime. During testing of p4p on the new GitHub OsX runners, which are all now arm64, we see a Bus Error:
/Users/runner/work/_temp/28281c48-3576-478b-b140-78e8b699ad51.sh: line 9: 3925 Bus error: 10 python -m nose2 -v p4p
In an ideal world we should fix the ARM64 code to allow use on modern MacOS systems. An alternative is to explicitly fail a compilation on a MacOS ARM platform (but leave it working for e.g. Rasberry Pi, which is the platform this code was originally written for).
Testing either of these fixes should be straightforward by using GitHub's macos-latest runner.
- Dominant language
- C
- Stars
- 13
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from DiamondLightSource/cothread
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DiamondLightSource/cothread#78 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DiamondLightSource/cothread#75 · 5 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
DiamondLightSource/cothread#73 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
DiamondLightSource/cothread#67 · 2 comments ·
All issues in DiamondLightSource/cothread
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
containers/bubblewrap#813 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tree-sitter/tree-sitter#6005 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
facebookincubator/muse-gadget-sdk#47 ·
Maintainers usually reply within 1 day