When DCHECK's trigger on my debug chromium build, I get an unsymbolized
stacktrace like
[7036:25234:31462940569:FATAL:net/ocsp/nss_ocsp.cc(251)] Check failed:
!request_.
[7036:25234:31462940569:FATAL:net/ocsp/nss_ocsp.cc(251)] Check failed:
!request_.
Backtrace:
out/Debug/chrome [0x8d7d9bc]
In http://codereview.chromium.org/428004, I introduced a new GYP target -
but don't have an msvs_guid for it.
I'm guessing that I can just use a value from VS Tools Create GUID, but
wanted to confirm this since I didn't see any documentation on generating
the guids.
Chris
--
Chromium
How do most people do cross-platform validation prior to submitting code?
Do you mostly rely on the try-bots, or do you also patch the diffs to your
different dev environments and build and test locally?
If you do the patching, do you tend to do a gcl upload and grab the diffs
from there, or do
Howdy,
I've been trying to dive into the Chromium codebase and have been
focusing on the network stack after getting the gist of how Chromium
on the whole is organized.
I've written a few hacky little command line tools to exercise some of
the networking components (nslookup-like for
. :-)
On Fri, Nov 13, 2009 at 11:13 AM, Chris Bentzel cbent...@gmail.com wrote:
Howdy,
I've been trying to dive into the Chromium codebase and have been
focusing on the network stack after getting the gist of how Chromium
on the whole is organized.
I've written a few hacky little command
A number of pages on dev.chromium.org reference scons/hammer as the
default tools for Linux builds.
I've been using make just fine for the past week.
If make is the standard tool now, I'll volunteer to clean up the documentation.
Chris
--
Chromium Developers mailing list:
