28

I am really getting frustrated with Google Chrome... I have version 3.0.195.27 and want to debug some JavaScript that is working in IE, FF but not in Chrome.

When I open the debugger and mark breakpoints (the blue arrow thingy) and execute the JavaScript it hits the breakpoint and then I do not know how to step through code....I tried all function keys .....F5 causes the whole window to refresh....

Typing next in console window does nothing.....

Plus the debugger is very slow to further add salt to the wounds...

BenMorel
  • 34,448
  • 50
  • 182
  • 322
Pankaj Kumar
  • 1,748
  • 6
  • 28
  • 41

4 Answers4

66

I'm on Chrome 3.0.195.27, and I'm able to use the following keys:

  • F8 -> Run

  • F10 -> Step over

  • F11 -> Step into

Make sure you have focus on the JavaScript console.

Christian C. Salvadó
  • 807,428
  • 183
  • 922
  • 838
4

Use the pause, step over, step into, step out buttons at the right end of the inspector, below the search field and above the watch/call stack section.

Jesper
  • 1
  • 1
3

In addition to the F8 (Run) F10 (Step over) and F11 (step into) you can single step your code by clicking on the line number at the left of each line and one at a time create a breakpoint on each line. Then by using F8 your code will run one line and stop at the next breakpoint. This has the effect of enabling you to single step through your code. If the next code line is a function then use F10 or F11 depending on the result you desire.

Someone voted down this answer, but didn't say why. A comment would be helpful. If you have a better way to single step through the code, please add a comment explaining your approach.

Rich
  • 41
  • 2
  • The better way to step through the code is not to use breakpoints on every line. – Nathan Tuggy Mar 31 '17 at 02:55
  • @NathanTuggy Do you know of another way. I was looking here and this seems like the only suggestion. – cdignam Jan 20 '18 at 05:21
  • @cdignam: Well, the answer mentions the two better ways but does not explore them, instead recommending the ridiculously cumbersome technique of creating as many breakpoints as there are lines to step through. But F10 and F11 *already step by one statement*. So sure, set a breakpoint, but you only need *one* breakpoint to get to where you can single-step. – Nathan Tuggy Jan 20 '18 at 06:53
  • @NathanTuggy > But F10 and F11 already step by one statement. This is simply not true. They step over "next function call", which is entirely different. – Vasily Pankratov Mar 22 '18 at 14:06
  • 1
    @foverzar: F10 and F11 single-step exactly as much as "breakpoint every line" silliness. – Nathan Tuggy Mar 22 '18 at 20:12
-1

I recommend you to debug with FireBug. It is the absolutely best tool for it.

I have Chrome version 4.0.221.6, and there i got a button list where i can step in / step through

so maybe you need to update your Chrome version?

Patsy Issa
  • 11,113
  • 4
  • 55
  • 74
k0ni
  • 2,417
  • 4
  • 22
  • 25