SubmoduleCollection#each segfaults in bare repo
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 293
- PR merge metrics
- No merged PRs in 30d
Description
repo = Rugged::Repository.new("<path to repo that has a .gitmodules file, but is bare>")
repo.submodules.each{}; nil # segfaults
I've reproed on Mac and Linux, both times not using the system libgit2.
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 provided Rugged::Repository example with a bare repository containing a .gitmodules file, then inspect SubmoduleCollection#each and the repo.submodules entry point. Done means iterating submodules no longer segfaults in bare repositories, with the behavior verified on the reported platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, git, ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100