Comment #8 on issue 6500 by [email protected]: Chrome: Crash Report -
Stack Signature: DebugUtil::BreakDebugger()-77D5E4
http://code.google.com/p/chromium/issues/detail?id=6500
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=8989
------------------------------------------------------------------------
r8989 | [email protected] | 2009-01-30 13:33:29 -0800 (Fri, 30 Jan 2009) | 8
lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/tcp_client_socket.h?r1=8989&r2=8988
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/tcp_client_socket_win.cc?r1=8989&r2=8988
In rare cases (when running inside QEMU), the event
object is not yet in the signaled state after a
Winsock function succeeds synchronously, so it is
necessary to wait for it to become signaled.
R=eroman
BUG=6500
Review URL: http://codereview.chromium.org/19515
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
