It has been reported to me in private that it is possible for Peanut-GB to call NULL as a function if a spurious write to 0xFF50 happens. If gb_bootrom_read is not set by the frontend implementation, Peanut-GB could end up calling NULL as a function point when reading the first 0x100 bytes of ROM bank 0.
It has been reported to me in private that it is possible for Peanut-GB to call NULL as a function if a spurious write to 0xFF50 happens. If gb_bootrom_read is not set by the frontend implementation, Peanut-GB could end up calling NULL as a function point when reading the first 0x100 bytes of ROM bank 0.
Thank you to the anonymous reporter.