Jeremy Evans c5c05460ac Warn on access/modify of $SAFE, and remove effects of modifying $SAFE ... This removes the security features added by $SAFE = 1, and warns for access or modification of $SAFE from Ruby-level, as well as warning when calling all public C functions related to $SAFE. This modifies some internal functions that took a safe level argument to no longer take the argument. rb_require_safe now warns, rb_require_string has been added as a version that takes a VALUE and does not warn. One public C function that still takes a safe level argument and that this doesn't warn for is rb_eval_cmd. We may want to consider adding an alternative method that does not take a safe level argument, and warn for rb_eval_cmd.		2019-11-18 01:00:25 +02:00
..
-test-
minitest	tool/lib/leakchecker.rb: show the code location that allocated leaked fd	2019-11-12 01:47:18 +09:00
test	Add debug print	2019-11-09 15:20:52 +09:00
colorize.rb
envutil.rb
find_executable.rb
iseq_loader_checker.rb
jisx0208.rb
leakchecker.rb	Warn on access/modify of $SAFE, and remove effects of modifying $SAFE	2019-11-18 01:00:25 +02:00
memory_status.rb
profile_test_all.rb
tracepointchecker.rb
vcs.rb	make-snapshot: Regexp#match raises on nil now	2019-10-22 21:05:52 +09:00
vpath.rb
zombie_hunter.rb