Re: [chromium-dev] Symbolized backtrace on Linux chromium?

2009-12-08 Thread 王重傑
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-p

Re: [chromium-dev] Symbolized backtrace on Linux chromium?

2009-11-30 Thread Evan Martin
On Mon, Nov 30, 2009 at 11:16 AM, Michael Moss 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'

Re: [chromium-dev] Symbolized backtrace on Linux chromium?

2009-11-30 Thread Michael Moss
On Mon, Nov 30, 2009 at 9:58 AM, Evan Martin wrote: > On Mon, Nov 30, 2009 at 9:37 AM, Chris Bentzel 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_. >> [703

Re: [chromium-dev] Symbolized backtrace on Linux chromium?

2009-11-30 Thread Craig Schlenter
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 wrote: > When DCHECK's trigger on my debug chromium build, I get an unsymbolized > stacktrace like > [7036:25234:31462940569:FATAL:net/ocsp/nss_ocsp

Re: [chromium-dev] Symbolized backtrace on Linux chromium?

2009-11-30 Thread Evan Martin
On Mon, Nov 30, 2009 at 9:37 AM, Chris Bentzel 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 f

Re: [chromium-dev] Symbolized backtrace on Linux chromium?

2009-11-30 Thread 陈智昌
On Mon, Nov 30, 2009 at 9:37 AM, Chris Bentzel 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 f

[chromium-dev] Symbolized backtrace on Linux chromium?

2009-11-30 Thread Chris Bentzel
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/D