On Mon, 15 Aug 2022 at 15:55, Jonathan Cameron via <qemu-...@nongnu.org> wrote: > In the interests of defensive / correct handling from QEMU I took a > look into why it was crashing. Turns out that providing a NULL write > callback for > the memory device region (that the above overlarge write was spilling into) > isn't > a safe thing to do. Needs a stub. Oops.
Yeah. We've talked before about adding an assert so that that kind of "missing function" bug is caught at device creation rather than only if the guest tries to access the device, but we never quite got around to it... -- PMM
