Emulator

Try versions before 4.0-905 out of curiosity.

Can you do that and still build dolphin yourself? Regular dolphin works, but I am trying to build with fastlog.

Is it a debugfast build? Would a straight up debug build work? Basically, I'm thinking the MMIO merge is causing this.

I couldn't figure out how to build for regular debug. I couldn't find any documentation on this. The only thing I could determine from the code is that cmake -DFASTLOG=ON .. builds for debugfast. DO you know how to build for just regular debug?

Right... Mac. I'll just have to try to reproduce on my own. I'll see what I can do.

thx. I'm sorry, couldn't get my hands on a half decent pc.

-DCMAKE_BUILD_TYPE=Debug, I believe.

It built correctly but still gives the same error. Any other ideas?

I just downloaded the source from 3.5 and 3.0 dolphins and I can't even get those to build. I got errors on both.

This error message also appears on Windows 7 if you build with Debug x64 and launch with the "-debug" parameter (4.0-3186).

Tried to run GC Zelda OoT / MQ Disc PAL - md5: b18019b6b399c9826bae843f06c43d08 (D43P01),
so I believe this is not limited to Mac or a specific game (unless I just happened to catch the right game...)

the address variable passed to UniqueID() is 4294967288 ( 0xfffffff8 )

Stacktrace:
KernelBase.dll!000007fefde13ca2()
DolphinD.exe!MMIO::UniqueID(unsigned int address) Line 58
DolphinD.exe!MMIO::Mapping::GetHandlerForWrite(unsigned int addr) Line 129
DolphinD.exe!MMIO::Mapping::Write(unsigned int addr, unsigned int val) Line 112
DolphinD.exe!Memory::WriteToHardware(unsigned int em_address, const unsigned int data, unsigned int effective_address, Memory::XCheckTLBFlag flag) Line 180
DolphinD.exe!Memory::Write_U32(const unsigned int _Data, const unsigned int _Address) Line 402
[External Code]

I hope this helps tracking it down

I'm getting the same issue. Linux x64 (Fedora); recent GitHub (from the past couple weeks); built in DebugFast mode; tested with Starfox Assault (USA version). When I launch the game in debug mode, I get the panic alert "EXTERNAL_INT unrecoverable???", followed by an endless sequence of "Trying to get the ID of a non-existing MMIO address." 4.0.2 doesn't have this issue. If panic alerts are disabled, the dialogs don't appear, but instead the game window stays gray and the game never starts.

As far as I can tell, the bug I described was introduced between 4.0-3042 and 4.0-3049. However, I think that commit was after this issue thread was started. So, maybe there are two unrelated bugs here?

I've honestly never had issues with this, so there isn't much I can do to help.

Maybe someone else can take a look at this?

If this helps at all, other things aren't working as well. the memcheck menu isn't popping up for me. I don't know if that helps out at all. I can still click next to a line of code to add a blue square, but it doesn't do anything. I have tried this on dolphin 3, 3.5, and 4. As of last time I tried, I could only get 3.5 and 4+ to build and the issue was present in both. Hope that helps.

@kacmlwei, yeah, so we seem to have two distinct bugs that produce the same error message in different situations. The bug I'm encountering was introduced long after 4.0.2 came out, and it prevents even booting the game in debug mode.

@biolizar, I had that same also had that problem. I fixed it by messing with check boxes in the settings. I forgot which one tho. Is it giving you a gray screen?

I'm just curious, has anyone either succeeded or failed to reproduce my symptoms on Linux? I assume lots of people use Dolphin on Linux, but I guess I don't know that for certain.

@kacmlwei, Yes, the game window stays gray for me when I run a game in debug mode. If panic alerts are enabled, I get the endless sequence of MMIO errors when the game launches (and the game windows stays gray); if panic alerts are disabled, no errors appear but the game window stays gray.

try turning off cheats

For me the bug occurs regardless of whether cheats are enabled/disabled.

nvm, the gray screen bug no longer occurs for me... somehow.

For what it's worth, I tried a fresh profile; it didn't help; the bug still occurs. So I suspect it's not related to a profile setting.

So, looking at the pull request that introduced the issue I'm encountering, it looks like the offending commit is 8dea26762dcc842ebcb227c0b9b9bbefc487624c ("Rationalize temporary register usage"). The previous commit in that PR, 67cdb6e07a9c1c3ddbfd6e61036756259344e289, works fine.

Maybe this will help in tracking down the bug?

I just rebuilt dolphin again for the first time in a while, and now its not even playing the game. I'm getting this error. Not sure if this is related to the original bug or not. Mem check menu still not displaying.

Warning:
"EXTERNAL_INT unrecoverable???"

Dolphin then crashes. The output into the terminal while running dolphin is posted at http://pastebin.com/N6TaJHkM

hope that helps

@kacmlwei Sounds like you've got the same issue as me, then. When I click No at that panic alert, Dolphin crashes; if I click Yes, I get the MMIO address panic alert.

@kacmlwei You're on OS X, right?

@biolizar yep. The difference with mine is that dolphin crashes with either button.

The issue is fixed for me in latest Git master.

The pop up box issue is indeed fixed. the memcheck breakpoints bar is still broken though, should I open a new issue?

Yes, please open up a new issue after determining which revision the issue started at.

Thanks for confirming that the issue is fixed, kacmlweimer