Currently, VS Code does not deal with unreadable bytes in readMemory requests, so that's just treated as the "end of file"/end of memory range. However that's a very temporary solution.

Currently there's two ways I could see for this to be signalled:

• Via unreadableBytes. In the end of file case, the "number of bytes that must be skipped before a subsequent 'readMemory' request will succeed" is, however, infinite, which cannot be expressed as a numeric JSON type.
• By having the data being shorter than the number of requested bytes (0 the offset is at or after the end of the sequence). If this is something that implementors should depend on, we should document it explicitly.