[wasm][debugger] Assertion caused by invalid array id being used

[radical]

This can be seen in DebuggerTests.ArrayTests.InvalidArrayId, which gets an assertion:

console.error: * Assertion at /workspaces/runtime/src/mono/mono/metadata/class.c:4580, condition ' not met`

mono_array_element_size (MonoClass *ac)
{
        g_assert (m_class_get_rank (ac));

We should validate validate whether a given object is an array or not, before calling into these functions.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This can be seen in DebuggerTests.ArrayTests.InvalidArrayId, which gets an assertion:

console.error: * Assertion at /workspaces/runtime/src/mono/mono/metadata/class.c:4580, condition ' not met`

mono_array_element_size (MonoClass *ac)
{
        g_assert (m_class_get_rank (ac));

We should validate validate whether a given object is an array or not, before calling into these functions.

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

[radical]

cc @thaystg

[lewing]

is this still an issue?