19 replies to this topic

[Heaven/TQA]

I was just wondering for weeks now how can I disassemble memory location and then simply disassemble next page?

on most debuggers I am doing stuff like D 4000 and then a simple D while the next page is displayed. and in Altirra?

[flashjazzcat]

Scroll wheel works for me - just pull it down and it keeps disassembling.

[andym00]

U

Seriously.. U 4000

Better using the windows for this stuff, then you can just page up and down through memory..

[Heaven/TQA]

aem... no?
u 4000 gives me one page, then hitting page down, cursor down no effect?

[andym00]

Debug->window->disassembly..

[flashjazzcat]

I'd assumed you were using the disassembly window.

[Heaven/TQA]

aehm.... no... oldschool command line? or what are you guys using most?

[Heaven/TQA]

ok. disassemly windows works but is there a way to show only the mnemonics without the memory dump? ok not a big deal but could help in copy/pase code.

[andym00]

Not that I know of.. But surely whatever editor you're using allows you to do a rectangular select ?
In VisualStudio it's shift+alt to select a rectangular region..

[Heaven/TQA]

and another question compared with Atari800 debugger... save state? how? the quickstate is not saveable for later?

[flashjazzcat]

Personally I'd like to see the windowed memory dump scroll like the disassembly window, but preferably up and down.

Edited by flashjazzcat, Sun Feb 26, 2012 6:30 AM.

[Heaven/TQA]

my editor is notepad

[Rybags]

You can copy from the Dissasembly window (as well as probably most others).
I often do traceblits with breakpoints, grab a couple of frames worth of trace and copy out the lot.

Select the block of text and use CTRL-C

Agreed, there's certain commands that need to continue their listing if you just enter them without parameters.

Edited by Rybags, Sun Feb 26, 2012 6:37 AM.

[andym00]

Memory window scrolling would be nice, but I keep four memory windows open, each doing 256 bytes in size, so mostly that's enough for me..
As for Heaven and his editor.. Get a new editor

[Heaven/TQA]

any ideas regarding save state?

[andym00]

I've never used it in Altirra, and not quite sure what you're asking about actually

[andym00]

Oh, I see, I think.. In the debugger you can't do a quick savestate because "it's in the middle of an instruction"..

[Heaven/TQA]

Well... Save States help when you have a special condition to test... Or in a game to avoid the play through of levels. Atari800win can load save states.

[Creature XL]

Savestates never worked for me. Neither from debugger nor when just running the debugee. But I did not try for long. Would be interested if you succeed.

[phaeron]

I never bothered to implement continuations for the disassembly command out of laziness. The .dumpdsm command will dump a disassembly to disk, and in 2.10 test-13 it has been expanded to support options that allow you to turn off code bytes, EA decoding, etc.

Current versions don't allow you to save states to a file because the file format isn't stable enough yet. The emulator stopping in the middle of an instruction is one of the factors that complicates this.