One command line tool I have sometimes wanted when debugging, is a way to dump out a cached response from the disk cache.
The only way I know to do this currently is create a profile and load it in chrome, then use about:cache to print the response as hex. (At which point you still need to unhexify it and then reverse any filters like bzip2 before you have the content) On Fri, Nov 13, 2009 at 5:46 PM, Wan-Teh Chang <w...@google.com> wrote: > On Fri, Nov 13, 2009 at 11:58 AM, Chris Bentzel <cbent...@gmail.com> wrote: >> I'm using them as a learning exercise for the network stack - and I'm >> guessing that they will help debug behavior in the future as well. >> >> I don't intend to add additional functionality over the standard tools >> - in fact, I promise you they'll be less functional than the standard >> tools. For example, my hresolv executable just takes a hostname and a >> port as options for now. >> >> I'll spend a bit more time getting them to a reasonable point and send >> a patch out for review - figure decision will be easier then over a >> vague description. > > I also like the idea. These tools can serve as sample code > for other projects that are considering taking our network > stack. It can also be easier to debug a simple command > line tool than a full-blown browser if a network stack bug > can be reproduced using a command line tool. > > Wan-Teh > > -- > 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
