Lol. No doubt I'm way off, which is why I gave up in frustration and came here. 
I don't think what you're suggesting is what I'm after though, and in fact the debugger never breaks with those watchpoints, at least not when in the test menu's sound check screen.
What I was hoping to have happen is break in the debugger when it starts accessing certain sounds in order to see how those sounds are handled. Particularly, where a sound clip starts and where it ends, with the ultimate goal of replacing some sound clips altogether. That's why I was looking at the 140000 and beyond memory range. Any suggestions on how I might accomplish this?
Thanks for the help.
|
Index 
Flat 
Re: MAME debugger question
Reply
