Has anyone managed to run dolphin in valgrind with recent master? When I try, I get a bunch of "Executable memory ended up above 2GB!", and then dolphin goes piff.
When I run with memcheck, I see:
Does it just not work right now? Are there some tricks I don't know to get it to work?
When I run with memcheck, I see:
Code:
==7357== Thread 4:
==7357== Invalid write of size 1
==7357== at 0x6A4355: Gen::XEmitter::AlignCode16() (x64Emitter.cpp:88)
==7357== by 0x600C32: Jit64AsmRoutineManager::Generate() (JitAsm.cpp:38)
==7357== by 0x602C57: Jit64::Init() (JitAsm.h:32)
==7357== by 0x5F8D0F: JitInterface::InitJitCore(int) (JitInterface.cpp:84)
==7357== by 0x5F2376: PowerPC::Init(int) (PowerPC.cpp:144)
==7357== by 0x59C1B8: CCPU::Init(int) (CPU.cpp:30)
==7357== by 0x5ABFDD: HW::Init() (HW.cpp:48)
==7357== by 0x5689E0: Core::EmuThread() (Core.cpp:354)
==7357== by 0x60D778F: ??? (in /usr/lib64/libstdc++.so.6.0.19)
==7357== by 0x3348007F32: start_thread (in /usr/lib64/libpthread-2.18.so)
==7357== by 0x33474F4DEC: clone (in /usr/lib64/libc-2.18.so)
==7357== Address 0xffffffffffffffff is not stack'd, malloc'd or (recently) free'dDoes it just not work right now? Are there some tricks I don't know to get it to work?