You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some google searching I found that it is generally due to the gem dependencies.
I am using
ruby version : ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]
rails version : Rails 5.0.1
Is the error due to the gem incompatibilty? If yes, how can it be fixed?
The text was updated successfully, but these errors were encountered:
RishabhKr97
changed the title
Segmentation fault while reading valuse
Segmentation fault while reading values
Feb 10, 2017
I have recently had the same issue. It turns out that only integers can be added to a trie along with a word. That is, even though trie.add('word', 'some other text') would run perfectly fine, trying trie.get('word') would cause a segmentation fault. However, trie.get('word') works perfectly fine after adding an integer (e.g., trie.add('word', 1) ). It seems it has been 7 years but I hope this saves somebody some debugging time.
I am getting a segmentation fault while reading data from trie. First three-four reads doesn't give segmentation fault but it appears after that.
The trie is created by the following code
I am using the following code to read from trie
After some google searching I found that it is generally due to the gem dependencies.
I am using
ruby version : ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]
rails version : Rails 5.0.1
Is the error due to the gem incompatibilty? If yes, how can it be fixed?
The text was updated successfully, but these errors were encountered: