Luke Gruber 0d367ce65f Fix bad NameError raised using sendforward instruction through vcall
If you called a VCALL method and the method takes forwarding arguments
and then you forward those arguments along using the sendforward
instruction, the method_missing class was wrongly chosen as NameError
instead of NoMethodError. This is because the VM looked at the CallInfo
of the vcall and determined it needed to raise NameError. Now we detect
that case and raise NoMethodError.

[Backport #21535]
2025-08-27 15:19:58 -07:00
..
2025-02-27 09:00:25 -08:00
2025-07-15 09:23:42 -07:00
2025-04-03 15:32:20 -07:00
2024-11-25 08:00:03 +00:00
2024-11-20 16:59:55 +00:00
2025-04-09 16:02:37 -07:00
2025-02-27 09:00:25 -08:00
2024-12-03 06:49:56 +00:00