sorbet: srb tc segfault
Input
https://github.com/will/sorbetsegfault
srb tc
Observed output
/Users/will/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5585/bin/srb:
line 46: 58729 Segmentation fault: 11 "${sorbet}" "${args[@]}"
Expected behavior
not segfault
/t/sorbetseqf (master)> bundle info sorbet
* sorbet (0.5.5585)
Summary: A Typechecker for Ruby
Homepage: https://sorbet.run
Path: /Users/will/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5585
/t/sorbetseqf (master)> ruby -v
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-darwin19]
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 7
- Comments: 16 (7 by maintainers)
Just realized I’d begun bundling for deployment.
bundle exec srb tc --ignore=vendor/fixed the issue for me. Sharing in case others find helpful.This segfaults for me also, on GNU/Linux, with sorbet 0.5.5685 and ruby 2.6.6p146.
I think I isolated the issue:
Makes sorbet segfault: https://sorbet.run/#%23 typed%3A true class Foo include Enumerable end class Bar < Foo Elem %3D type_member(%3Aout) end
This is what is happening with the definition in out.rbi coupled with
DataSetincludingEnumerablein sequel.rbi.getting segfault after switch to ruby 2.7.1 and sorbet update (platform MacOS)
debug and backtrace
I am also seeing the seg fault.
@dduugg’s suggestion did not work. Any other ideas?
What does it take for this to become a confirmed bug?
We’re getting this error on ruby 2.6.5 on EC2 instances running AWS Linux 2. CI reports:
Not sure what we can do to get a deeper stack trace output. If it would be helpful to add more info, let me know how we can produce it and I’ll be glad to post it.