in mrbgems/mruby-bin-debugger.

According to the valgrind log attached to #3438, proc->body.irep
may be NULL in some cases.

Maybe related to #3438

Dinko Galetic and Denis Kasak reported the issue and the fix.
(via https://hackerone.com/dgaletic).

Fix interpolation escaping in String.inspect

Kernel#local_variables: Make result array unique

http://hkdnet.hatenablog.com/entry/2017/02/06/080000 (Japanese)

Now `eval()` can call Fiber.yield etc.

Calling `mrb_funcall()` and `mrb_yield()` (and their related
functions) are discouraged unless absolutely necessary, because
it can cause this kind of issues very easily.

Fix usage of Class#name in mruby-bin-mruby's bintest

Fetch arguments earlier in mrb_random_init to avoid a crash.

ref #3411

This issue was first reported by https://hackerone.com/geeknik
The fix was proposed by @titanous

The fix was proposed by @titanous

This issue was reported by https://hackerone.com/ston3

Refactoring: Use array_copy instead of for loop

The new API is:

int mrb_range_beg_len(mrb, range, &beg, &len, len, trunc)

The new argument `trunc` is a boolean value that specifies
whether the function truncates the range. The new return value
is an integer instead of a boolean, that is:

 0: not a range
 1: range with proper edges
 2: out of range

To get the old behavior, you have to rewrite:

  mrb_range_beg_len(mrb, range, &beg, &len, len)

to:

  mrn_range_beg_len(mrb, range, &beg, &len, len, TRUE) == 1

[Breaking Change]

ref #3409

Rewrite mrb_ary_splice