-
Notifications
You must be signed in to change notification settings - Fork 13
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
cyclone68k is causing invalid memory accesses #2
Comments
There is not enough information to help you here (something like backtrace with register dump would be helpful), and I don't have time to figure out how to build/use your project, sorry. It looks like you have removed the whole thing anyway? Compressed jumptable was off in your config, so it's something else. |
Since the lowest power ARM platform I am targeting is the New 3DS I removed cyclone because I think using the local memory handlers in musashi will be enough to get it up to speed, that is true, but when I find a bug I try to get it fixed regardless of it will benefit my personal emulation goals. I was not saying compressed jumptable was causing this issue, I was saying I originally thought it was the cause of the SIGSEGVs, but it wasnt, turning it off just masked the issue. Here is a register dump but the stack trace is lacking, it is compiled in debug mode, but I think the stack may be corrupted so it cant get a trace:
|
Exact version of emu:
meepingsnesroms/Mu@adbd803
Crashes regardless of if compiled for RetroArch or Qt.
To trigger a crash turn the emulated device off then back on.
I have had issues like this before and attributed it to the compressed jump table.
Back then it crashed on boot with a invalid memory access.
For the Qt build some opcodes are renamed but for the libretro build its using the output of your newest version.
This is the config.h used to build it as well:
https://github.com/meepingsnesroms/Mu/blob/master/src/m68k/cyclone/config.h
It works fine with musashi(and always has) so I know its not an emulator side issue.
If there is any more information you need to know I will gladly provide it.
The text was updated successfully, but these errors were encountered: