Value of the SR register in WinUAE debugger

[kamelito]

Is the value of the SR register in WinUAE debugger displayed somewhere?
The value of the différents bits is but the actual value of SR?

[a/b]

It's not, that's one of the things I'd like to see as well. It would also be good to see the VBR (I'm talking about the UI).

EDIT: I'm a do-it-yourself guy, but winuae build env has always been a roadblock for me (gcc?)...
Is it as sinple as this (debug_win32.cpp)? There is more than enough room for 2 more lines.

	hwnd = GetDlgItem(hDbgWnd, IDC_DBG_SP_VBR);
	_stprintf(out, _T("USP: %08X"), regs.usp);
	UpdateListboxString(hwnd, 0, out, TRUE);
	_stprintf(out, _T("ISP: %08X"), regs.isp);
	UpdateListboxString(hwnd, 1, out, TRUE);
 _stprintf(out, _T("SR: %04X"), regs.sr);
 UpdateListboxString(hwnd, 2, out, TRUE);
 _stprintf(out, _T("VBR: %08X"), regs.vbr);
 UpdateListboxString(hwnd, 3, out, TRUE);

	ShowMiscCPU(GetDlgItem(hDbgWnd, IDC_DBG_MISCCPU));

[Toni Wilen]

Yeah, it should be included too. Done.

[Falcon]

Originally Posted by a/b

EDIT: I'm a do-it-yourself guy, but winuae build env has always been a roadblock for me (gcc?)...

I actually managed to install Visual Studio 2022 Community Edition with all required components on Windows 10 and build WinUAE from source - ended up being a fairly painless process. I then added some code to work around a Wine keyboard handling discrepancy and even submitted a pull request for it on GitHub.

Linux Mint is my main OS, but I use Windows for gaming (performance reasons) and some testing.

[a/b]

Originally Posted by Falcon

... install Visual Studio 2022 Community Edition .. Windows 10

x + y = overflow :P. That thing does not work on my windoze7. Tried installing several times, straight up crashes or refuses to work. I guess being tripple muzzled and not being able to do whatever the mothership commands is a problem :P.

In any case, I see that SR is now there but it looks like it's out of sync with the individual bits. E.g. I hit shift+f12 during boot and see something like:
- SR 2000, but x = 1, nzvc = 0, or
- SR 2000, but xn = 1, zvc = 0
Then step (t) through several instructions, bits get updated but SR is still at 2000.
Then after, while in userland, shift+f12 into ROM interrupt code:
- SR 0000, but S = 1, IMASK = 3, x = 1, nzvc = 0

After some digging, my best guess is that you have to call MakeSR() to construct the correct value out of all the individual bits prior to using it as regs.sr.

Also, vbr? Somewhere, anywhere? ;p It's actually part of the dialog ID but it's not there ;p.

[Waccoon]

I'm currently building with VS 2019 under Win7 and it works fine. However, I have to turn off address sanitation for the Test build or it blows up.

I'm not sure what's going on, but I wouldn't be surprised if VS just doesn't support the feature under Win7 and it doesn't tell you.

[a/b]

Thanks, will check it out next time I feel pressured enough to install it ;p. Switching to/from debug config would often freeze the whole thing and only "kill -9" helped ;p, so maybe that was it.

[kamelito]

Another annoying thing is when you trace you don’t see what you’re tracing. I need to disassemble after each trace and I’m not even sure if the PC register is displayed we saw more next PC.

[Toni Wilen]

Originally Posted by a/b

After some digging, my best guess is that you have to call MakeSR() to construct the correct value out of all the individual bits prior to using it as regs.sr.

Yeah, MakeSR() was missing. Will be fixed.

Originally Posted by Waccoon

I'm currently building with VS 2019 under Win7 and it works fine. However, I have to turn off address sanitation for the Test build or it blows up.

Address sanitizer has never worked if 32-bit build. It works if 64-bit build.

[Waccoon]

Originally Posted by Toni Wilen

Address sanitizer has never worked if 32-bit build. It works if 64-bit build.

Not like it's a big deal, but I am doing a 64-bit build. When the executable is created, some extra library files are dumped into the destination test folder and when WinUAE is launched, it complains about a DLL entry point being wrong.

I don't use VS for any other projects, so I never bothered to look too much into how its linker works. Maybe I don't have a necessary module installed or something. I'll worry about it later.