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
