Issue 3772: Distributed reliability test failures with NewHTTP
http://code.google.com/p/chromium/issues/detail?id=3772
Comment #6 by [EMAIL PROTECTED]:
The results from instrumentation confirm the virtual dispatch on bad object
theory.
The magic value put on the stack is 0xDEADBEFC, which means we didn't make
it past GetSSLInfo() before crashing:
Bug3772Set(bug_3772_state, 12); // Push 0xDEADBEFB
if (using_ssl_ && !establishing_tunnel_) {
Bug3772Set(bug_3772_state, 13); // Push 0xDEADBEFC
SSLClientSocket* ssl_socket =
reinterpret_cast<SSLClientSocket*>(connection_.socket());
ssl_socket->GetSSLInfo(&response_.ssl_info);
}
Bug3772Set(bug_3772_state, 14); // Push 0xDEADBEFD
return OK;
So now the next question to answer is why this->connection_.socket() was
bad.
--
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
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to chromium-bugs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
