-
Notifications
You must be signed in to change notification settings - Fork 60
Segmentation fault when re-building #99
Comments
I think the issue has to deal with the fact that we've loaded the library in memory when we run Might be able to fix this by not loading the entire application when our require_relative 'config/application'
Rails.application.load_tasks so that might be rather difficult... You can see that |
Issue is with |
Ah interesting, we've done a lot of our active testing on macOS which behaves a bit differently in this area. Probably the solution would be to detect the |
is there a temporary workaround that doesnt involve rebuilding everything? my rust crate is rather large |
Confirmed on Ruby 2.2, Rails 3.2 on Debian Jessie. |
It builds without error on first
rake build
run, but then I get segmentation fault on the followingrake build
runs. Error dissapears when I runrake clobber
before each run to clean stuff. Even when segmentation fault error shows, it looks like it's doing a good build. It seems to be consistently happening across all Ruby versions for me and is caused by the require ofnative.so
.Output for ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]:
Output for ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]:
Output for ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]:
The text was updated successfully, but these errors were encountered: