[wasm][debugger] Evaluate methods with short arguments

[ilonatommy]

We do not have a mechanism of detecting if literal is short, so both options from each case:

• short and int
• sbyte and byte
• uint and ushort
  are falling into the non-short category in MonoSdbHelper.WriteNumbers. The simplest fix for it that comes to my mind is a mechanism of InvokeMethod retries every time we detect a numeric literal that is of type int/byte/uint. With multiple parameters that classify for retry, the number of retries grows exponentially which is not the best solution.

Uncomment

// ("test.SumDefaultNegativeAndRequiredParamShortInts(-1, -120)", TNumber(-121)),
// ("test.SumDefaultNegativeAndRequiredParamShortInts(-1)", TNumber(-124)), // default: -123
// ("test.GetDefaultNegativeShortInt(-123)", TNumber(-123)),

in EvaluateMethodWithDefaultParam test. Current behavior:
"No implementation of method 'GetDefaultNegativeShortInt' matching 'test.GetDefaultNegativeShortInt(-123)' found in type DebuggerTests.DefaultParamMethods.TestClass.",

Coreclr behavior for the short int tests scenarios:

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

We do not have a mechanism of detecting if literal is short, so both options from each case:

• short and int
• sbyte and byte
• uint and ushort
  are falling into the non-short category in MonoSdbHelper.WriteNumbers. The simplest fix for it that comes to my mind is a mechanism of InvokeMethod retries every time we detect a numeric literal that is of type int/byte/uint. With multiple parameters that classify for retry, the number of retries grows exponentially which is not the best solution.

Uncomment

// ("test.SumDefaultNegativeAndRequiredParamShortInts(-1, -120)", TNumber(-121)),
// ("test.SumDefaultNegativeAndRequiredParamShortInts(-1)", TNumber(-124)), // default: -123
// ("test.GetDefaultNegativeShortInt(-123)", TNumber(-123)),

in EvaluateMethodWithDefaultParam test. Current behavior:
"No implementation of method 'GetDefaultNegativeShortInt' matching 'test.GetDefaultNegativeShortInt(-123)' found in type DebuggerTests.DefaultParamMethods.TestClass.",

Coreclr behavior for the short int tests scenarios:

Author:	ilonatommy
Assignees:	-
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

[thaystg]

This is fixed by the new debugger.