Gorf #1 Posted December 14, 2009 (edited) Part of my fustration of finishing these 2 games is not being able to track what is going on. Im using the Prosystem Emu to dev with. Any suggestions? Edited December 14, 2009 by Gorf Quote Share this post Link to post Share on other sites
S1500 #2 Posted December 14, 2009 Doesn't MESS have some basic debugging features? Probably not dev-friendly, but it might give another angle. Quote Share this post Link to post Share on other sites
Gorf #3 Posted December 14, 2009 Doesn't MESS have some basic debugging features? Probably not dev-friendly, but it might give another angle. Well I was hoping for something more like the one stella has. Then I could trace what is going on. Quote Share this post Link to post Share on other sites
DanBoris #4 Posted December 15, 2009 Doesn't MESS have some basic debugging features? Probably not dev-friendly, but it might give another angle. Yes MESS has a very nice debugger in it. You can single step, trace to a file, view/edit memory, set conditional breakpoints, etc. Dan Quote Share this post Link to post Share on other sites
Gorf #5 Posted December 15, 2009 Doesn't MESS have some basic debugging features? Probably not dev-friendly, but it might give another angle. Yes MESS has a very nice debugger in it. You can single step, trace to a file, view/edit memory, set conditional breakpoints, etc. Dan Is this feature information in the docs? It seems that when you set the debug mode, it only pops up another screen and halts. Quote Share this post Link to post Share on other sites
carmel_andrews #6 Posted December 15, 2009 Doesn't MESS have some basic debugging features? Probably not dev-friendly, but it might give another angle. Yes MESS has a very nice debugger in it. You can single step, trace to a file, view/edit memory, set conditional breakpoints, etc. Dan Is this feature information in the docs? It seems that when you set the debug mode, it only pops up another screen and halts. Mr Gorf., you need to select the run option on the first tab on the debug screen for the game image to run (from what i recall)...it's a bit crappy on slow machines though and i'm using a D/C amd Quote Share this post Link to post Share on other sites
krewat #7 Posted December 16, 2009 I must say, having "been there, done that", MESS has a very nice debugger. I don't remember off-hand, but it was missing SOMETHING usefull, I forget what. But it's definitely a decent thing. I remember having to use a hardware 6502 emulator to REALLY debug the 7800. With my recent foray into debugging Impossible Mission, the MESS debugger was PERFECT. Quote Share this post Link to post Share on other sites
DanBoris #8 Posted December 18, 2009 Is this feature information in the docs? It seems that when you set the debug mode, it only pops up another screen and halts. Once you are in the debugger, just type HELP, it has extensive built in help. Dan Quote Share this post Link to post Share on other sites
Gorf #9 Posted December 18, 2009 Is this feature information in the docs? It seems that when you set the debug mode, it only pops up another screen and halts. Once you are in the debugger, just type HELP, it has extensive built in help. Dan I took a look....could not figure out how to stop the code from running once you set it to go. Quote Share this post Link to post Share on other sites
krewat #10 Posted December 18, 2009 (edited) I took a look....could not figure out how to stop the code from running once you set it to go. You have to set breakpoints and such, or single step it. Load the system, then type "go" in the debugger window. Once the program is running, type F11 or F10, which is a single step command. This will basically halt the program right where it is. Edited December 18, 2009 by krewat Quote Share this post Link to post Share on other sites