The editor doesn't handle correctly memory access errors

[AdrianOltean]

Description
Various memory areas in an embedded system can be inaccessible at some point, before an actual configuration/enablement. When Memory Inspector asks for memory to be read, the request eventually reaches a (GDB) debug server that might return a memory access error. Looks like Memory Inspector is not very good at handling such a situation and it simply reports "No results found".

How to reproduce:

1. NXP SDK, NXP LPC55S69 board, a J-Link debug probe. Should not matter as long as you can replicate what's written above.
2. MCUXpresso for VS Code extension installed.
3. Import a "Hello World" project using the MCUXpresso for VS Code extension.
4. Debug.
5. Start Memory Inspector and jump to address 0x20000000.
6. Load 128 more bytes above. At this point, address at 0x1FFFFF00 is inaccessible.

Or try to replicate the basic idea (assume some memory area is invalid and try to access it from Memory Inspector) by some other means, other setup.

Expected behavior
Memory Inspector should make it clear that memory cannot be accessed.

Environment

• OS: Windows 11
• Theia or VS Code Version: VS Code 1.96.4

Additional information

GDB debug server reports error but Memory Inspector simply shows "No results found":