[webkit-dev] Troubles with fresh WebKit build on Windows

[Anton Muhin]

Dear WebKiters,

I just git pulled WebKit:

commit 597a1d3006745f287ae2aba32edd7d3e353ed0d7
Author: barraclough at apple.com
<barraclough at apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Date:   Thu Oct 8 09:18:21 2009 +0000

    Fix for JIT'ed op_call instructions (evals, constructs, etc.)
    when !ENABLE(JIT_OPTIMIZE_CALL) && USE(JSVALUE32_64)

    Patch by Zoltan Herczeg <zherczeg at inf.u-szeged.hu> on 2009-10-08
    Reviewed by Gavin Barraclough.

    https://bugs.webkit.org/show_bug.cgi?id=30201

    * jit/JITCall.cpp:
    (JSC::JIT::compileOpCall):



    git-svn-id: http://svn.webkit.org/repository/webkit/trunk@49293
268f45cc-cd09-0410-ab3c-d52691b4dbfc

and did a clean build (manually removing WebKitBuild).  Now if I run
./WebKitTools/Scripts/run-safari it dies on startup.  Callstack:

>	Safari.dll!665832de() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for
Safari.dll]
 	kernel32.dll!_InternalFindAtom at 12()  + 0x8b bytes	
 	Safari.dll!66446884() 	
 	Safari.dll!66441663() 	
 	Safari.dll!664483de() 	
 	user32.dll!_UserCallWinProcCheckWow at 32()  + 0x10e bytes	
 	user32.dll!_CallWindowProcAorW at 24()  + 0x5e bytes	
 	user32.dll!_CallWindowProcW at 20()  + 0x1b bytes	
 	comctl32.dll!_CallOriginalWndProc at 24()  + 0x1a bytes	
 	comctl32.dll!_CallNextSubclassProc at 20()  + 0x3d bytes	
 	comctl32.dll!_DefSubclassProc at 16()  + 0x46 bytes	
 	comctl32.dll!TTSubclassProc()  + 0x3c bytes	
 	comctl32.dll!_CallNextSubclassProc at 20()  + 0x3d bytes	
 	comctl32.dll!_MasterSubclassProc at 16()  + 0x44 bytes	
 	user32.dll!_InternalCallWinProc at 20()  + 0x23 bytes	
 	user32.dll!_UserCallWinProcCheckWow at 32()  + 0xb7 bytes	
 	user32.dll!_DispatchMessageWorker at 8()  + 0xee bytes	
 	user32.dll!_DispatchMessageW at 4()  + 0xf bytes	
 	Safari.dll!664acb85() 	
 	comctl32.dll!_MasterSubclassProc at 16() 	
 	0033f384()	
 	user32.dll!_UserCallWinProcCheckWow at 32()  + 0xb7 bytes	
 	user32.dll!_DispatchClientMessage at 24()  + 0x51 bytes	
 	user32.dll!___fnDWORD at 4()  + 0x2b bytes	
 	ntdll.dll!_KiUserCallbackDispatcher at 12()  + 0x2e bytes	
 	comctl32.dll!_MasterSubclassProc at 16() 	
 	ntdll.dll!_NtdllDispatchMessage_W at 0() 	

Platform: Windows Vista 64, Miscrosoft Visual Studio 2005.

Has anyone see anything like that?  Are there any workarounds?

tia and yours,
anton.