We use V8 in the browser process to run the JS shell, from which it is possible to type V8 debugger commands. You can telnet to this shell (after running chrome with a special command line switch) or open up the "JS debugger" UI.
We will also soon be using V8 in the browser process to execute PAC scripts in the network library. (eroman is working on that.) -Darin On Mon, Feb 16, 2009 at 5:47 AM, Dean McNamee <de...@chromium.org> wrote: > > I thought the js debugger was out of process (or trying to be)? > > On Mon, Feb 16, 2009 at 1:29 PM, Marc-Antoine Ruel <mar...@chromium.org> > wrote: > > the js debugger > > > > On Mon, Feb 16, 2009 at 5:53 AM, Dean McNamee <de...@chromium.org> > wrote: > >> > >> What for? > >> > >> On Mon, Feb 16, 2009 at 12:18 AM, Erik Kay <erik...@chromium.org> > wrote: > >>> > >>> v8 is already in the browser process. > >>> > >>> Erik > >>> > >>> > >>> On Sun, Feb 15, 2009 at 1:46 PM, Evan Martin <e...@chromium.org> > wrote: > >>>> > >>>> Does this mean we'll have v8 in the browser process? > >>>> > >>>> We had idly chatted about running a 64-bit browser process to fix the > >>>> library hell on Linux. It shouldn't block you either way -- I'm just > >>>> curious. > >>>> > >>>> On Sun, Feb 15, 2009 at 1:42 AM, Aaron Boodman <a...@chromium.org> > wrote: > >>>>> > >>>>> I'm trying to commit a change > >>>>> (http://codereview.chromium.org/19737/diff/1440/1448 ) which adds a > >>>>> base class for unit tests that exercise JavaScript. It uses v8.h, > >>>>> which is disallowed by DEPS. What is the right way to do this? > >>>>> > >>>>> - a > >>>>> > >>>>> > > >>>>> > >>>> > >>>> > > >>>> > >>> > >>> > > >>> > >> > >> >> > >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
