mirror of
https://github.com/ruby/ruby.git
synced 2026-10-29 00:46:26 +08:00
Benoit DalozeandClaude Opus 5.5
9ba7257f44
Since the fix for Bug #21441, ec->cfp is set to NULL before clearing the VM stack so that thread_profile_frames() called from a signal handler returns early instead of walking a stack that is no longer set on the ec. But these are plain stores to distinct fields of the same struct, so the compiler is free to reorder them. With Apple clang 21 and GCC 16 on macOS arm64, and with clang 18 and GCC 13 on Linux aarch64, both stores of rb_ec_set_vm_stack() were combined into a single stp emitted before the store to ec->cfp (vm_stack is at offset 0, vm_stack_size at 0x8 and cfp at 0x10): stp xzr, xzr, [x0] ; ec->vm_stack = NULL, vm_stack_size = 0 str xzr, [x0, #0x10] ; ec->cfp = NULL ret So a signal in between would see a non-NULL ec->cfp with a NULL ec->vm_stack. Stopping there in lldb when a thread terminates and calling rb_profile_frames() segfaults in thread_profile_frames(), as end_cfp is computed from the NULL ec->vm_stack and the loop walks past the control frames. With this change, ec->cfp is already NULL at that point and rb_profile_frames() returns 0. Like in vm_push_frame(), use atomic_signal_fence() to keep the store to ec->cfp first. With it, all these compilers emit the store to ec->cfp no later than the stores clearing the stack. The rest of vm.o is unchanged with Apple clang 21, GCC 16 and GCC 13 on aarch64. Clang 21 and 18: stp xzr, xzr, [x0, #0x8] ; ec->vm_stack_size = 0, cfp = NULL str xzr, [x0] ; ec->vm_stack = NULL ret GCC 16 and 13: str xzr, [x0, #0x10] ; ec->cfp = NULL stp xzr, xzr, [x0] ; ec->vm_stack = NULL, vm_stack_size = 0 ret With GCC 13 on x86_64, the store to ec->cfp is already emitted first without the fence, and vm.o is identical with and without it: endbr64 movq $0x0, 0x10(%rdi) ; ec->cfp = NULL movq $0x0, (%rdi) ; ec->vm_stack = NULL movq $0x0, 0x8(%rdi) ; ec->vm_stack_size = 0 ret [Bug #22477] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What is Ruby?
Ruby is an interpreted object-oriented programming language often used for web development. It also offers many scripting features to process plain text and serialized files, or manage system tasks. It is simple, straightforward, and extensible.
Features of Ruby
- Simple Syntax
- Normal Object-oriented Features (e.g. class, method calls)
- Advanced Object-oriented Features (e.g. mix-in, singleton-method)
- Operator Overloading
- Exception Handling
- Iterators and Closures
- Garbage Collection
- Dynamic Loading of Object Files (on some architectures)
- Highly Portable (works on many Unix-like/POSIX compatible platforms as well as Windows, macOS, etc.) cf. https://docs.ruby-lang.org/en/master/maintainers_md.html#label-Platform+Maintainers
How to get Ruby
For a complete list of ways to install Ruby, including using third-party tools like rvm, see:
https://www.ruby-lang.org/en/downloads/
You can download release packages and the snapshot of the repository. If you want to download whole versions of Ruby, please visit https://www.ruby-lang.org/en/downloads/releases/.
Download with Git
The mirror of the Ruby source tree can be checked out with the following command:
$ git clone https://github.com/ruby/ruby.git
There are some other branches under development. Try the following command to see the list of branches:
$ git ls-remote https://github.com/ruby/ruby.git
You may also want to use https://git.ruby-lang.org/ruby.git (actual master of Ruby source) if you are a committer.
How to build
See Building Ruby
Ruby home page
Documentation
Mailing list
There is a mailing list to discuss Ruby. To subscribe to this list, please send the following phrase:
join
in the mail subject (not body) to the address ruby-talk-request@ml.ruby-lang.org.
Copying
See the file COPYING.
Feedback
Questions about the Ruby language can be asked on the Ruby-Talk mailing list or on websites like https://stackoverflow.com.
Bugs should be reported at https://bugs.ruby-lang.org. Read "Reporting Issues" for more information.
Contributing
See "Contributing to Ruby", which includes setup and build instructions.
The Author
Ruby was originally designed and developed by Yukihiro Matsumoto (Matz) in 1995.