shoestring Posted October 17, 2018 Share Posted October 17, 2018 Perhaps I didn't read the documentation well enough but I couldn't find anything that could trace the given CPU to a file, as in what MAME can do. trace {<filename>|OFF}[,<cpu>[,[noloop|logerror][,<action>]]] Anyone know if there is similar feature available ? Quote Link to comment Share on other sites More sharing options...
R0ger Posted October 17, 2018 Share Posted October 17, 2018 I've been asking similar question, and got some good advice here: http://atariage.com/forums/topic/273633-altirra-300-released/page-22 Look for my name on this page .. 2 Quote Link to comment Share on other sites More sharing options...
shoestring Posted October 17, 2018 Author Share Posted October 17, 2018 Thanks for the tip. That's going to be big help in the debugging process... Quote Link to comment Share on other sites More sharing options...
R0ger Posted October 17, 2018 Share Posted October 17, 2018 Also make sure you read this thread: http://atariage.com/forums/topic/216515-debugging-using-altirra/ 1 Quote Link to comment Share on other sites More sharing options...
phaeron Posted October 18, 2018 Share Posted October 18, 2018 You can do this with the .logopen and gt (go traced) commands, though it'll also spew to the console which will slow down execution. The History window is the recommended way to inspect execution in Altirra -- I stopped trying to dig through megabytes of execution trace logs a long time ago. 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.