The motto of this update of FCEUXD SP is definitely "This happens when you don't have unit tests for your code". I think each and every bug fixed in this version could have been picked up by even the most basic test framework.
Thankfully I found Kapow who worked as a human unit test on my website (see the comments for the last release) and on IRC. You can thank him for most of the new stuff and bugfixes in version 1.05.
Enough text, here's what you guys actually care about:
- New: Added range options for freezing / unfreezing addresses
- New: Added dump RAM to file option
- New: Added dump PPU memory to file option
- New: Readme file fceuxd.txt from FCE Ultra Extended Debugger is now included (read this if you want to learn about the debugger)
- Change: Increased the maximum number of frozen addresses
- Bugfix: NL files for banks at 0x8000 work again
- Bugfix: Empty comments work properly again
- Bugfix: Fixed a breakpoint persistence problem
There seems to be a bug with the debugging window. When adding text with smybollic debugging, mousing over and using the inline debugger from the vertical bar next to the window attempts to operate on the wrong address. It looks like it simply needs to account for the added lines of text to be fixed.
thanks for reporting this bug even though I've already been aware of it.
It's exactly what you've guessed. The inline assembler does not take into account the extra lines added by symbolic debugging.
That's because the inline assembler calculates the current address as a function of the pixel position of the mouse cursor relative to the top of the debugger window. Considering the additional lines would mean completely rewriting the entire thing.
I've not yet done that because I'm waiting for Parasyte's extremely cool debugging control which he made for the next version of FCE Ultra extended-debug (he posted pics some months ago at acmlm's board). I don't want to spend time rewriting the code now and then rewriting it again later.
One thing I'd like, is to have all the messages concerning the Hex Editor when you have an NSF playing be removed, so it can be used more easily.
The Hex Editor works great for debugging RAM based issues in NSF files(in conjunction with the debugger), but I need to use tricks to open it and copy/paste to use it effectively, when it already functions properly for my debugging needs, aside from the 'you can't use this with NSFs' message.
Love this new release - I'm currently using it to find enemy ASM in Zelda 2. This may be too much to request, but the ability to load a headerless ROM would be handy, if a new version is released. I know, I should just remember to add ten bytes to everything from RAM, but if easily feasible, this would certainly be a nice option. Great update!