I'll take a look.
If anyone has ideas on how to implement this (beyond looking at
base/debug_util.h) please let me know! The last time I messed around with
programatic stack traces was 5+ years ago. :-)
On Sat, Aug 8, 2009 at 7:53 AM, Dimitri Glazkov <dglaz...@chromium.org>wrote:
> Somebody please run with this! :)
>
> :DG<
>
> On Fri, Aug 7, 2009 at 8:45 PM, Darin Fisher<da...@chromium.org> wrote:
> > On Fri, Aug 7, 2009 at 8:39 PM, Ojan Vafai <o...@chromium.org> wrote:
> >>
> >> On Fri, Aug 7, 2009 at 8:45 PM, Jeremy Orlow <jor...@chromium.org>
> wrote:
> >>>
> >>> Has anyone ever looked into printing out stack traces when layout tests
> >>> crash? Of the couple layout test crashes I've investigated, I think
> most
> >>> could have been solved just by having a stack trace. I'm not really
> sure
> >>> what's involved or if anyone's looked into this, which is why I'm
> asking.
> >>> This could be especially helpful for flaky tests that crash.
> >>
> >> I don't remember anyone having looked into this. I agree that this would
> >> make tracking down and fixing these issues immensely easier, especially
> for
> >> tests that only sometimes crash.
> >> Ojan
> >
> > I've wanted this for a very long time. I think there might be a bug on
> it.
> > At any rate, we now have a nice utility in base/debug_util.h that can
> > provide a stack trace. I would love to see crash stacks on the buildbot.
> > It would probably help us eliminate a lot of flakiness!
> > -Darin
> > > >
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
