Re: [chromium-dev] Symbolized backtrace on Linux chromium?
addr2line is another possible option. addr2line -e sconsbuild/Debug/chrome 0x87d9bc This works even if -fvisbility=hidden. I think w/o address space layout randomization, it's...relatively deterministic (I think). So, given that, maybe it would be sensible to find a way to add a small post-process hook in the layout bots to look for something that matches the Backtrace format, and runs addr2line on the trace. Same thing could work for mac, though I forget what the name of the tool is there and I've been told this issue is moot on OsX 10.6. -Albert On Mon, Nov 30, 2009 at 11:22 AM, Evan Martin e...@chromium.org wrote: On Mon, Nov 30, 2009 at 11:16 AM, Michael Moss mm...@chromium.org wrote: We have a test covering this: ./out/Debug/base_unittests --gtest_filter=StackTrace* Running it locally reveals that it is broken -- but the bots still work? It looks like there isn't a debug builder that runs base_unittests. It's the release build that passes. Since I (probably) broke this, I will fix it. -- 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] 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
Re: [chromium-dev] Symbolized backtrace on Linux chromium?
On Mon, Nov 30, 2009 at 9:37 AM, Chris Bentzel cbent...@google.com wrote: 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? I'm not really sure, but it's sort of interesting that you do seem to get it for certain functions in the system libs. I noticed this issue too recently. I think it's been the case for perhaps the past few weeks or so. My almost completely ungrounded suspicion is it has to do with some of the changes Evan made to shrink the chrome binary size, but I haven't investigated. -- 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
Re: [chromium-dev] Symbolized backtrace on Linux chromium?
On Mon, Nov 30, 2009 at 9:37 AM, Chris Bentzel cbent...@google.com wrote: 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] [...] Is there a reason I'm not getting symbols to display here? We have a test covering this: ./out/Debug/base_unittests --gtest_filter=StackTrace* Running it locally reveals that it is broken -- but the bots still work? I am confused. It was likely r32254. Maybe you can experiment with putting that flag into the Release-only section of the build/common.gypi? -- 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] Symbolized backtrace on Linux chromium?
The bug that is triggering here might be 28526 btw. ... ukai has a patch in review for that. --Craig On Mon, Nov 30, 2009 at 7:37 PM, Chris Bentzel cbent...@google.com wrote: 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 Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Symbolized backtrace on Linux chromium?
On Mon, Nov 30, 2009 at 9:58 AM, Evan Martin e...@chromium.org wrote: On Mon, Nov 30, 2009 at 9:37 AM, Chris Bentzel cbent...@google.com wrote: 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] [...] Is there a reason I'm not getting symbols to display here? We have a test covering this: ./out/Debug/base_unittests --gtest_filter=StackTrace* Running it locally reveals that it is broken -- but the bots still work? It looks like there isn't a debug builder that runs base_unittests. It's the release build that passes. Michael -- 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] Symbolized backtrace on Linux chromium?
On Mon, Nov 30, 2009 at 11:16 AM, Michael Moss mm...@chromium.org wrote: We have a test covering this: ./out/Debug/base_unittests --gtest_filter=StackTrace* Running it locally reveals that it is broken -- but the bots still work? It looks like there isn't a debug builder that runs base_unittests. It's the release build that passes. Since I (probably) broke this, I will fix it. -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev