Threading segfaults
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 92
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Are threads supposed to work?
This code triggers a segmentation fault:
t1 = UV::Thread.new do
puts "Thread 1"
end
t2 = UV::Thread.new do
puts "Thread 2"
end
t1.join
t2.join
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 running the reported Ruby example using UV::Thread and capture the segmentation fault. Trace the threading implementation and verify that both threads can be created, joined, and print their messages without crashing; the issue names no source files or tests to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100