I think you should file bugs if you can repro DCHECKs on trunk. On Mon, Nov 24, 2008 at 5:47 AM, Berend-Jan Wever <[EMAIL PROTECTED]> wrote: > You can use my "get_chromium.cmd" tool to automatically sync, clean and > build Chromium. I myself use a shortcut that syncs, builds and then switches > off my computer, which I run every day after work. That way I always have a > recent build to play with in the morning (unless the build broke). > I'm ignoring debug breaks in my fuzzing at the moment. I'm not finding many > crashes anymore so I start reporting debug breaks again. I expect my fuzzers > will find a lot (they used to anyway), but the whole process is highly > automated and I end up with a small repro and some useful information from > the debugger (like stack trace etc) so it's not very painful for me to file > the bugs. Can somebody advice me whether this would be useful at this point? > Cheers, > SkyLined > > Berend-Jan "SkyLined" Wever > Security Software Engineer > [EMAIL PROTECTED] > (Chromium/WebKit/V8: [EMAIL PROTECTED]) > Google Netherlands B.V. Reg: Claude Debussylaan 34, 15th > floor 1082 MD Amsterdam 34198589 Netherlands VAT / Tax ID:- 812788515 B01 > > > > On Fri, Nov 21, 2008 at 19:10, Ian Fette <[EMAIL PROTECTED]> wrote: >> >> It might be even more helpful (albeit painful) to run a debug build and >> start filing bug reports on all the DCHECKs. I stopped doing this around the >> webkit merge, but I'm switching back and hitting a ton of DCHECKs in gmail. >> >> On Wed, Nov 19, 2008 at 1:29 PM, Paul Godavari <[EMAIL PROTECTED]> wrote: >>> >>> It would be very helpful to also run these trunk builds with the command >>> line flag: --new-safe-browsing >>> This is our new SafeBrowsing storage implementation which we believe >>> greatly reduces disk IO that some have reported. Please file any bugs you >>> encounter and assign them to me. >>> Paul >>> >>> On Wed, Nov 19, 2008 at 1:17 PM, Nicolas Sylvain <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> >>>> On Wed, Nov 19, 2008 at 1:15 PM, Ben Goodger (Google) <[EMAIL PROTECTED]> >>>> wrote: >>>>> >>>>> As Chromium developers we should all be using recent trunk builds. >>>>> Just using the dev channel isn't good enough, as it doesn't have a >>>>> majority of the code changes that have occurred on the trunk, and also >>>>> tends to update only once a week or so. >>>>> >>>>> Quality on the trunk has taken a severe beating over the past few >>>>> weeks and I think it'd benefit from having everyone use it for their >>>>> day to day browsing. Right now, we don't have a good update strategy >>>>> for these bleeding edge builds, so just grab ones off buildbot: >>>>> >>>>> http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/ >>>> >>>> No, please use that one : >>>> http://build.chromium.org/buildbot/continuous/LATEST/ >>>> It's always updated to the latest green build. This is the one you >>>> should use. >>>> Nicolas >>>> >>>>> >>>>> -Ben >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
