[Linux] simple injection with LD_PRELOAD

[HardcorEViruS]

uint64_t myguid = ((uint64_t (*)())0x004D3790)();

This works for me. I'm running 3.3.5.12340 at the moment. How do you get this address? If I search with IDA I only get the address I posted before.
Thanks for your help.

[eLaps]

How do you get this address?

reading here :/

[audible83]

The patch that sednogma / fenris supplied in the first post of this topic is in place in the latest souces of Wine. just a heads up.

[flo8464]

Beware that WoW calls glClear() multiple times per frame though. I recommend to use the glXSwapBuffers() hook which is described below.

Is anyone able to confirm that?
I can't use the glXSwapBuffers hook as I distribute a tool for WoW and I don't really want to force people to patch and compile Wine.

I measured the frequence WoW calls glGlear and my results are even below the framecount displayed by WoW itself.
It's always like 15 fps shown by WoW and 13-14 calls to glClear.

So I assume the fps displayed by WoW are inaccurate and glClear is just fine if you don't attempt to paint yourself.

[_Mike]

Is anyone able to confirm that?
I can't use the glXSwapBuffers hook as I distribute a tool for WoW and I don't really want to force people to patch and compile Wine.

I measured the frequence WoW calls glGlear and my results are even below the framecount displayed by WoW itself.
It's always like 15 fps shown by WoW and 13-14 calls to glClear.

So I assume the fps displayed by WoW are inaccurate and glClear is just fine if you don't attempt to paint yourself.

I haven't tried running wow under wine, but I know that it calls clear multiple times per frame under d3d at least. (3 times iirc)
A simple way to test it would be to hook both glClear and glXSwapBuffers to see how many clears there are between each buffer swap.
And as long as you don't do your own rendering it shouldn't matter much even if they do clear more than once if your hook runs fast enough to not impact the fps to much.

[!@^^@!]

Another solution would be to write a "code FPS" mechanic where you count the given number of clears in a second and calculate what n'th clear call your code should run at to retain the code fps specified

[kouteiheika]

I can't use the glXSwapBuffers hook as I distribute a tool for WoW and I don't really want to force people to patch and compile Wine.

You can always redistribute your patched /usr/lib/wine/opengl32.dll.so with your tool and tell your users to replace their version with yours. Wine generally works pretty well even when you mix and match its libraries, especially with components like opengl32.dll.so that basically don't change at all between versions. I'm still using 1.3.11's gdi32 patched with DIB engine on 1.3.23 and I don't have any problems, so I doubt something as rarely touched as opengl32.dll.so will break anything.

[Skazzi]

ATM, wow crashed on

		if( read_uint(0x00A70C50) ) {
			p1 = read_uint(0x00A70C50);
			p2 = read_uint(p1 + 0x38);
			p_base = read_uint(p2 + 0x24);
		}

Ubuntu 64-bit 12.04 with ptrace_scope=0

Unhandled exception: page fault on read access to 0xc11456c1 in 32-bit code (0xf77176ee).