[chromium-dev] Symbolized backtrace on Linux chromium?
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] out/Debug/chrome [0x8d99838] out/Debug/chrome [0x8fba726] out/Debug/chrome [0x8fb7f7b] out/Debug/chrome [0x8fb7f8f] out/Debug/chrome [0x8fb90e1] out/Debug/chrome [0x8fb9444] /usr/lib/libnss3.so.1d [0xb7884ed4] /usr/lib/libnss3.so.1d [0xb788ed68] /usr/lib/libnss3.so.1d [0xb783533a] /usr/lib/libnss3.so.1d [0xb7836020] /usr/lib/libnss3.so.1d [0xb784e8dd] /usr/lib/libnss3.so.1d [0xb7852527] /usr/lib/libnss3.so.1d [0xb78535a7] /usr/lib/libnss3.so.1d [0xb7858548] /usr/lib/libnss3.so.1d [0xb785a5b6] /usr/lib/libnss3.so.1d(CERT_PKIXVerifyCert+0x464) [0xb77d7ce4] out/Debug/chrome [0x90ee205] out/Debug/chrome [0x90eeed7] out/Debug/chrome [0x90b3ed5] out/Debug/chrome [0x90b399e] out/Debug/chrome [0x90b39d9] out/Debug/chrome [0xa00ec3c] out/Debug/chrome [0x8dafe2e] /lib/tls/i686/cmov/libpthread.so.0 [0xb77044fb] /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb73a2e5e] It looks like this was built with the -g option, and file out/Debug/chrome shows that it's not stripped. This was built from head this morning. Is there a reason I'm not getting symbols to display here? -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] How do I generate an msvs_guid for the GYP file?
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 Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] workflow for cross-platform development
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 you copy the diffs from machine to machine prior to the upload? If you do an initial gcl upload, do you skip the trybots until you validate that it works on all platforms to reduce load on the trybots? Have there been any thoughts about adding gcl patch and unpatch commands which will grab the file diffs as well as duplicate the CL metadata in src/.svn/gcl_info? Sorry if this is a FAQ - but I couldn't find anything covering this on dev.chromium.org or by searching the chromium-dev group archive. Chris -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] Any interest in command line tools for network stack?
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 HostResolver, wget-like for HttpNetworkTransaction). Should I spend time trying to flesh these out and add to net/tools, or is this something which doesn't belong in the chromium codebase? Thanks, Chris -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Any interest in command line tools for network stack?
I'm using them as a learning exercise for the network stack - and I'm guessing that they will help debug behavior in the future as well. I don't intend to add additional functionality over the standard tools - in fact, I promise you they'll be less functional than the standard tools. For example, my hresolv executable just takes a hostname and a port as options for now. I'll spend a bit more time getting them to a reasonable point and send a patch out for review - figure decision will be easier then over a vague description. Thanks, Chris On Fri, Nov 13, 2009 at 2:49 PM, Jeremy Orlow jor...@chromium.org wrote: What's the intended purpose of such tools? Do they offer any functionality beyond the standard tools? Do you envision them being helpful to people debugging the Chromium network stack? (Me replying does in no way imply that I have the authority to say yes or no, btw. :-) 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 line tools to exercise some of the networking components (nslookup-like for HostResolver, wget-like for HttpNetworkTransaction). Should I spend time trying to flesh these out and add to net/tools, or is this something which doesn't belong in the chromium codebase? Thanks, Chris -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] Do people still use scons to build anymore?
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: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
