Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rugged-1.1.0 lib/rugged/repository.rb:257: [BUG] Segmentation fault at 0x0000000000000000 #864

Open
boyke opened this issue Jan 11, 2021 · 3 comments

Comments

@boyke
Copy link

boyke commented Jan 11, 2021

I'm running /opt/puppetlabs/puppet/bin/r10k deploy environment but this results in

/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.5.8p224 (2020-03-31 revision 67882) [x86_64-linux]

-- Control frame information -----------------------------------------------
c:0027 p:---- s:0175 e:000174 CFUNC :fetch
c:0026 p:0060 s:0169 e:000168 METHOD /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257
c:0025 p:0015 s:0162 e:000161 BLOCK /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/r10k-3.7.0/lib/r10k/git/rugged/bare_repository.rb:67

@carlosmn
Copy link
Member

We don't have knowledge or expertise in this project to know what this r10k project does or how it uses rugged. It does look like it could be a bug in rugged or libgit2 as it shouldn't ever segfault, but without seeing the code or how rugged was called, I don't see how we can investigate. The project that is crashing for you should be able to move on this.

@boyke
Copy link
Author

boyke commented Jan 11, 2021

Allright, will check that (there) first.

@djberg96
Copy link

I wonder if you're hitting the same thing we hit at #859

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants