Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vamos hitting InvalidCPUStateError #215

Open
SongbirdPro opened this issue Dec 28, 2024 · 1 comment
Open

Vamos hitting InvalidCPUStateError #215

SongbirdPro opened this issue Dec 28, 2024 · 1 comment

Comments

@SongbirdPro
Copy link

I've been using vamos for the past year, and it's great! However I am encountering a CPU exception on the latest project I'm working on:

c:\WinUAE\Work\uv>vamos -q tools\asm art\cart.sprites.src
Epyx HandyAsm 1.12 by Sassenrath Research, Ukiah CA

$cbff was last address
06:44:22.568 machine: ERROR: ----- ERROR in CPU Run #1 -----
06:44:22.568 machine: ERROR: Run: 'WinUAE\Work\uv\tools\asm': Initial PC=00210c, SP=013a64
06:44:22.569 machine: ERROR: PC=00000404 SR=----- USP=00013a08 ISP=000006fa MSP=00000780
06:44:22.569 machine: ERROR: D0=00000148 D1=00000000 D2=00018bd0 D3=00000000 D4=00000000 D5=00000000 D6=00000000 D7=00000000
06:44:22.569 machine: ERROR: A0=00002c53 A1=00001ae8 A2=00013be0 A3=00000000 A4=00013146 A5=00013a20 A6=00001ae8 A7=000006fa
06:44:22.570 machine: ERROR: SP-32=000000 SP-28=000000 SP-24=000000 SP-20=000000 SP-16=000000 SP-12=000000 SP-08=000000 SP-04=000000
06:44:22.570 machine: ERROR: SP+00=7000000 SP+04=a8da0000 SP+08=000000 SP+12=000000 SP+16=000000 SP+20=000000 SP+24=000000 SP+28=000000
06:44:22.570 machine: ERROR: InvalidCPUStateError: Invalid CPU State: pc=00a8da: m68k Exception: sr=0700
06:44:22.570 main: ERROR: vamos failed!

image

Any idea what the failure is, or how to avoid it?

@cnvogelg
Copy link
Owner

Unfortunately, with the error alone I can't see too much...

But you could run vamps with -IB -L debug.log to get a complete instruction trace of your program run.
Just attach the debug.log here...

If its possible then you could also share the binary and the necessary data so I could reproduce the issue here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants