From: SourceForge.net <no...@so...> - 2006-02-11 21:15:55
|
Feature Requests item #1388822, was opened at 2005-12-23 12:50 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421864&aid=1388822&group_id=38274 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Debugger Group: None >Status: Closed Priority: 5 Submitted By: Manuel Bilderbeek (manuelbi) >Assigned to: Manuel Bilderbeek (manuelbi) Summary: UMR detector Initial Comment: We encountered a problem the other day with "Namake's Bridgedrome". It was caused by an UMR in the MSX program itself. That's why I thought it might be nice to have an UMR detector built in the openMSX debugger. openMSX could simply keep track of which bytes in RAM were written to and which not. In case a byte gets read which was not written to before, openMSX can give a warning, or log it or something. Why find out UMR's manually while openMSX can perfectly automate it for you? An extra could be a check if the PC gets in uninitialized memory. ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2006-02-11 22:15 Message: Logged In: YES user_id=78178 Implemented. Use the new umr_callback setting: set it to a TCL proc and it will be called every time an UMR is detected (for devices that use CheckedRam only!). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421864&aid=1388822&group_id=38274 |