[Wine] Re: LogParser.exe

StrangeWill wineforum-user at winehq.org
Wed Apr 13 08:38:51 CDT 2011


Ok, so an update in case anyone stumbles across this.

I've decided to start removing stubs and putting placeholders in my branched code, seeing what other methods I need... if I needed just RtlCreateTagHeap I'd just write it... right?

Oops wrong.

First, RtlCreateTagHeap isn't documented like RtlCreateHeap is, so to implement it is going to be a pain, even other libraries that have RtlCreateTagHeap in them have them as stubs...

Secondly, if I replace the stub so it acts implemented, I get this:


Code:

fixme:ntdll:NtQuerySystemInformation (0x00000032,0x32fb28,0x00000004,(nil)) stub
wine: Call from 0x7bc4d670 to unimplemented function ntdll.dll.RtlGetNativeSystemInformation, aborting




So I'm pretty much looking at having to implement a good chunk of NtQuerySystemInformation for WINE, and I can't even begin to guess how deep this rabbit hole goes. Worse yet this has a stub, but is commented out, I wonder why.

And again, RtlGetNativeSystemInformation seems to be another piece of API that doesn't have documentation the public can access, and because of this I'm having massive problems implementing a placeholder to see how much of ntdll.dll would have to be written for this one program...

So barring anyone having suggestions on this, the command line utility LogParser.exe on WINE is a no go unless a lot of undocumented library calls are basically reverse engineered?







More information about the wine-users mailing list