[Question] Using _getObjectByGuid();?

[-Ryuk-]

Hello all,

Well it seems that _getObjectByGuid(); has changed the 4.2.

Im using

        public static uint GetObjectByGuid = 0x8C6F0; //

Pre 4.2 it was

_getObjectByGuid(localPlayerGuid, -1)

Now according to IDA it is

__cdecl ClntObjMgrObjectPtr(WGUID guid, TypeMask mask, char *file, int line);

How should I be using this?


EDIT:

On the other hand, if anyone knows a better way to do this, please share :P

[flo8464]

I was reversing some piece of code that used it yesterday, nothing changed if I am not completly wrong.
You might take a look at some lua function, most of the retrieve the local players guid and object ptr at the beginning.

[lanman92]

The signature to GetObjectByGUID has always been funky in IDA. WoW calls it with extra information or something. Those values that are pushed onto the stack are removed after the call is complete(__cdecl convention).

EDIT: Now that I think about it, you could add as many parameters to the function as you like, so long as you have the first 2 correct.

[flo8464]

You could stop using HexRays for everything.
I don't know which version you're using, but HexRays 1.1 often produces crap.

[-Ryuk-]

Hurm, then something else is causing my WoW closure :P

[jjaa]

You could stop using HexRays for everything.
I don't know which version you're using, but HexRays 1.1 often produces crap.

If you give Hex-Rays Decompiler incorrect type information, you can hardly expect it to produce accurate output. However, i do agree that people should learn to read the ASM when they see something iffy.

@OP the type info for the function has debug/ptr related stuff. SErrDisplayAppFatal in the debug/ptr build uses that information.

[MaiN]

It will also show up in a stack dump when WoW crashes.

[-Ryuk-]

It will also show up in a stack dump when WoW crashes.

I didnt get a crash... Just like a forced closure.

Its like I went into the Process Explorer and ended the Wow.exe process.
and it happens just after I use
_getObjectByGuid