| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
because one of the debugger tests failed. I filed a V8 issue
to fix the debugger tests properly:
http://code.google.com/p/v8/issues/detail?id=230
Review URL: http://codereview.chromium.org/21235
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9530 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/19423
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8802 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/14012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@6884 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
XXX.
Format frame numbers with two digits when presenting the output from teh f command.
BUG=1304224
Review URL: http://codereview.chromium.org/6079
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@3091 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
change in V8 where the implicit breaks currently issued when receiving
a command while running will be removed. To get in contact with the
V8 debugging interface and send messages V8 needs to be in the break
state. Getting V8 into the break state will be the responsebility of the
debugger using the V8 debugging interface.
Changed the messages between the renderer and the debugger. There are now
explicit messages for break and detach. Alse renamed the SendToDebugger
message to DebugCommand. There is now messages DebugAttach, DebugBreak,
DebugCommand and DebugDetach. The message DebugBreak has a force flag
to indicate whether the renderer should issue some JavaScript to help
the break along or whether it should just schedule a break to happen
whenever JavaScript executes.
Removed the artificial attach JSON response send by the renderer and
replaced that with an on debug attach call to the debugger shell. This
call is reouted to the on_attach function in the debugger JavScript code.
Changed the debugger to issue break requests whenever a suitable command,
e.g. setting a break point, is issued. In this case a flag is used to
track whether execution should be automatically resumed after the command
have been send to the V8 debugger interface. Changed the handling of the
plain break event to not force a break by executing additional JavaScript.
Thereby a plain break does not break JavaScript execution until code on
the tab beeing debugged is actually executed.
Set the command name explicitly on all commands.
Removed parseSimpleCommand as it was just used for the the continue command
for which an explicit parseContinueCommand has been added.
Removed the last_command field from DebugShell as it was not used.
Updated the debugger protocol test to reflect the removed attach event.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@1526 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
the command line arguments for the debugger tests:
Separate "--expose-debug-as debugContext" into two
arguments.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@1380 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
string.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@1379 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
arguments to the V8 shell sample.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@1376 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
The Chrome debugger tests use mjsunit.js from the V8 test framework. In the transition to a new structure for V8 on code.google.com the location of this file will change. A local copy is added temporaly to the debugger tests directory which can be removed when Chrome starts to use V8 from code.google.com.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@867 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
shell sample.
Removed the v8_shell project from the Chrome solution and added
v8_shell_sample instead.
Changed the Chrome JavaScript debugger tests to use v8_shell_sample instead
of v8_shell.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@862 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the last of its native UI. This is done using a DOMUIHost subclass and a new TabContents type.
This checkin also fixes a few minor issues:
* hitting the keyboard accelerator brings the current debugger window to front
* text is grayed out when in "running" mode rather than "paused"
* up/down arrows have command-line history (transient)
* some text used to get eaten when you first bring up the window ("attached to <tabname>"), this is now handled
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180 0039d316-1c4b-4281-b951-d872f2087c98
|
|
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15 0039d316-1c4b-4281-b951-d872f2087c98
|