debugger (new) disasm view misaligned

[JoakimLarsson]

I have just fetched the latest including the huge disasm commit and built it.

When entering the debugger in an 8088 myb3k session the first debugger disasm view is wrong, check address fffff here: https://i.imgur.com/bjAqWZM.png and repeatedly issue a softreset or just singelstep the first few lines of code. Seems like the wrap to address 0 is a problem here

Next single step over 0xfe035 the next line is just below the window: https://i.imgur.com/ZPjle6L.png

[angelosa]

Same issue for 68k based CPUs: http://mamedev.emulab.it/kale/fast/files/Clipboard01x.png Instruction at 0x786 doesn't take next displacement word. It's supposed to be bne $7a8 aka 0x6600 0x0020

[rb6502]

Also seeing weirdness with 68k.

[galibert]

68k is fixed, I messed up a qsort -> std::sort conversion. I'll look at the other issue.

OG.

On Mon, Nov 27, 2017 at 5:13 AM, R. Belmont notifications@github.com wrote:

Also seeing weirdness with 68k.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mamedev/mame/issues/2851#issuecomment-347074584, or mute the thread https://github.com/notifications/unsubscribe-auth/AI0i8WJoifWTc5-OWAvsWLUzGVMPfdwKks5s6jbRgaJpZM4Qq7wh .

[galibert]

All fixed, I think.

[JoakimLarsson]

Yep, I rebased now, the misalignment was gone

[JoakimLarsson]

I am not sure this is caused by the new disasm or an old debugger problem but I have never seen another address range being intermixed in the disassembler window with the current range before: https://i.imgur.com/S8zbAsG.png This happened when I stepped into and SHIFT-F11 out of a division with zero