archive/ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2025-08-25 05:55:46 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Use dedicated methods to abort

Browse source 
When `RUBY_DEBUG` is set, accessing a class in an invalid object will
cause a breakpoint trap instead of a segfault on some implementations.
This commit is contained in:
Nobuyoshi Nakada 2024-03-24 01:40:17 +09:00
parent 678cb80033
commit 8265a7531f
No known key found for this signature in database
GPG key ID: 3582D74E1FEE4465
3 changed files with 351 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

28
ext/-test-/fatal/invalid.c Normal file
View file

@ -0,0 +1,28 @@
#include <ruby.h>
#if SIZEOF_LONG == SIZEOF_VOIDP
# define NUM2PTR(x) (void *)NUM2ULONG(x)
#elif SIZEOF_LONG_LONG == SIZEOF_VOIDP
# define NUM2PTR(x) (void *)NUM2ULL(x)
#endif
static VALUE
invalid_call(VALUE obj, VALUE address)
{
typedef VALUE (*func_type)(VALUE);
return (*(func_type)NUM2PTR(address))(obj);
}
static VALUE
invalid_access(VALUE obj, VALUE address)
{
return *(VALUE *)NUM2PTR(address) == obj ? Qtrue : Qfalse;
}
void
Init_invalid(VALUE mBug)
{
rb_define_singleton_method(mBug, "invalid_call", invalid_call, 1);
rb_define_singleton_method(mBug, "invalid_access", invalid_access, 1);
}