Select Unit causes Fatal Error

[haku43]

2 different approaches cause the same error:

This application has encountered a critical error:

ERROR #134 (0x85100086) Fatal Condition

WoWBuild: 12340

//GGGameUI_Target  3.3.5 0x00524BF0
[UnmanagedFunctionPointer(CallingConvention.Cdecl)]
public delegate void SelectUnitDelegate(ulong guid);
public static SelectUnitDelegate SelectUnit;

            uint codeCave = wow.AllocateMemory(0x108);

            wow.WriteUInt64(codeCave + 0x100, guid);

            wow.Asm.Clear();
            wow.Asm.AddLine("MOV EAX, [0x{0}]", (codeCave + 0x100 + 0x4).ToString("X"));
            wow.Asm.AddLine("PUSH EAX");
            wow.Asm.AddLine("MOV EAX, [0x{0}]", (codeCave + 0x100 + 0x0).ToString("X"));
            wow.Asm.AddLine("PUSH EAX");
            wow.Asm.AddLine("CALL 0x00524BF0");
            wow.Asm.AddLine("ADD esp, 0x08");
            wow.Asm.AddLine("RETN");

            wow.Asm.InjectAndExecute(codeCave);

[lanman92]

Rebase the address. It's relative to wow's base.

This will also probably fail 50% of the time unless you are in wow's main thread.

[culino]

He's using WoW 3.3.5, under normal conditions he don't have to rebase anything.

[haku43]

I gave up, and use this method:

ProcessManager.Memory.SuspendThread();
ProcessManager.Memory.WriteUInt64((uint)Pointers.WowLocalPlayer.LastTargetGUID,guid);
ProcessManager.Memory.ResumeThread();
ProcessManager.Player.TargetLastTarget();

[JuJuBoSc]

You don't really need to suspend thread for this kind of tasks

[lanman92]

It could potentially cause a race condition because he's writing 8 bytes, which is normally going to be two writes. His thread could be suspended in between the writes, then what happens if WoW tries to access that address?