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

[Anton Muhin]

Thanks a lot, Adam.

I've attached my crash dump to the bug, maybe it'd help.

Does anybody know any recent healthy revision to sync to?

yours,
anton.

On Thu, Oct 8, 2009 at 7:12 PM, Adam Roben <aroben at apple.com> wrote:
> On Oct 8, 2009, at 10:54 AM, Anton Muhin wrote:
>
>> 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?
>
> This looks like <https://bugs.webkit.org/show_bug.cgi?id=30085>. We don't
> have a workaround yet.
>
> -Adam
>
>