Finish implementing gdb non-stop mode
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Punted from 0.1. The gdb in fedora 19 really really wants us to be using it, and when we don't, it manifests a bug (#459) that appears to be caused by assuming that the stub is using non-stop when it isn't.
Contributor 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.
Research direction
Start by reviewing the existing gdb integration and issue #459 to understand how the stub currently assumes non-stop mode. Investigate what “finish implementing gdb non-stop mode” requires for Fedora 19 compatibility; done means the stub and gdb no longer rely on conflicting stop-mode assumptions and the affected behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, fedora, linux
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100