http://bugs.winehq.org/show_bug.cgi?id=27476
--- Comment #11 from Hans Leidekker hans@meelstraat.net 2011-11-21 01:56:24 CST --- (In reply to comment #4)
trace:winhttp:WinHttpConnect 0x1, L"api.facebook.com", 443, 0 ... trace:winhttp:WinHttpConnect returning 0x6 trace:winhttp:WinHttpOpenRequest 0x6, L"GET", L"/method/facebook.fql.multiquery?access_token=AAAAAKLSe4lIBAL3F2dweZCSRUFrpJM3ZAUumCBWoyYU68fpnl6EYVgbq6gzYUmJe3BBlpu8OAzvDxL62ZCPOGsCqkq6agAZD&format=json&queries=%7b%22friends_query%22%3a%22SELECT+uid%2c+name%2c+username%2c+pic_square_with_logo%2c+pic%2c+pic_small%2c+pic_big%2c+online_presence%2c+pr"..., (null), (null), (nil), 0x00800000
... trace:winhttp:process_header L"Host": L"graph.facebook.com" 0x10000000 trace:winhttp:get_header_index L"Host" trace:winhttp:get_header_index returning -1 trace:winhttp:process_header L"Connection": L"Keep-Alive" 0x10000000 trace:winhttp:get_header_index L"Connection" trace:winhttp:get_header_index returning -1 trace:winhttp:send_callback 0x10a92ea0, 0x00000001, 0x10b00bd8, 19 trace:seh:raise_exception code=c0000005 flags=0 addr=0x7bc3469a ip=7bc3469a tid=000d
Looks like the app doesn't expect that WINHTTP_CALLBACK_STATUS_RESOLVING_NAME callback at this point. Please attach a full +winhttp trace.