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

Resolve segfault issue #50

Open
tonywok opened this issue Aug 9, 2023 · 5 comments
Open

Resolve segfault issue #50

tonywok opened this issue Aug 9, 2023 · 5 comments
Assignees
Labels

Comments

@tonywok
Copy link
Member

tonywok commented Aug 9, 2023

Duplicated by #45, #43, and I think #40

I'm able to reproduce this pretty reliably. Going to mark the above issues as duplicates. Let me know if for some reason you think they are distinct.

Seems to happen when I run rake run, but not rake 🤔. Will have to dig in when I get some time (hoping this week since I'm off work for a few days).

@tonywok tonywok added the bug label Aug 9, 2023
@tonywok tonywok self-assigned this Aug 9, 2023
@mlk-kc
Copy link

mlk-kc commented Sep 7, 2023

HI @tonywok : I thought I'd best add a segfault issue to this issue's thread rather than opening a new issue? I'm receiving a segfault when working through the about_regular_expressions.rb file. I believe its caused simply because there are too many tests in the file 😅 After I complete the test_shortcut_character_classes_are_negated_with_capitals test, any other test that is attempted within this file causes the seg fault. However, if I comment out the remaining tests in the file, running path_to_enlightenment.rb will happily start looking at the next file (about_control_statements.rb).

I'm running 13.5.1 (22G90) MacOS on a Macbook Pro with a 2.3 GHz 8-Core Intel Core i9 processor and 16 GB 2667 MHz DDR4 memory. My current Ruby version is ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-darwin22] managed by rbenv.

Hope this helps!

@tonywok
Copy link
Member Author

tonywok commented Sep 7, 2023

@mlk-kc Thank you! Yes, I'm still hopeful this is all the same root issue -- or at least caused from the same class of issue. Hoping to get some time to dive deeper in the coming days (been a bit heads down on work-work).

Glad you found a work-around.

@mlk-kc
Copy link

mlk-kc commented Sep 7, 2023

No problem at all 😄 If I can provide any extra information, please let me know!

@geoffreyvanwyk
Copy link

I got past the segmentation fault by switching from 3.2.2 to 3.0.6.

@Wolwer1nE
Copy link

Thanks to @WarLockeR31 we found out that there is no segfault in Ruby 3.2.3.
So we may update, not downgrade version.

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

No branches or pull requests

4 participants