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