96cde52838
An invalid ROM dataspace can occur, for example, when requesting a ROM from the report_rom service before the first report was posted. Such a <rom> node can still be useful if it's dynamic. E.g., it can be watched. Hence, the corner case of an invalid ROM dataspace should be gracefully handled instead of causing an abort. Issue #3606 |
||
|---|---|---|
| .. | ||
| block_file_system.h | ||
| file_system_factory.cc | ||
| fs_file_system.h | ||
| inline_file_system.h | ||
| log_file_system.h | ||
| null_file_system.h | ||
| ram_file_system.h | ||
| rom_file_system.h | ||
| rtc_file_system.h | ||
| symlink_file_system.h | ||
| tar_file_system.h | ||
| terminal_file_system.h | ||
| zero_file_system.h | ||