967759 - Remove unnecessary eval calls from frontend tests

Status: RESOLVED WONTFIX

(DevTools :: Debugger, defect, P3)

Description

[Jim Blandy :jimb]

In bug 322176, we made the line numbers reported for eval more reasonable. However, it runs afoul of the many debugger front-end mochitests that have text like:

function firstCall() {
  eval("secondCall();");
}

...

function secondCall() {
  // This comment is useful: ☺
  eval("debugger;");
  function foo() {}
  if (true) {
    foo();
  }
}

Before bug 332176, the eval code would be attributed to the line containing the eval call. Post-patch, the eval code is attributed to line 1 --- of the *evaluated* code. So all those mochitests had their expected line numbers changed from something like "6" or "18" to, simply, 1.

It turns out that those 'eval' calls are not essential to the tests. They predate the implementation of Debugger.prototype.findScripts, to a time when onNewScript notifications were the only way for the debugger to see a script --- so the tests used 'eval' to ensure that those notifications were generated. But we don't need them any more.

Since the 'eval' calls effectively erase meaningful information --- at what location were we executing? --- they should be removed from the debuggee code, and the original, meaningful line numbers reinstated.

(Kannan volunteered on IRC to take this on.)

Comment 1

[Eddy Bruel [:ejpbruel]]

Kannan, are you still volunteering for this?

Comment 2

[Kannan Vijayan [:djvj]]

Not volunteering for this anymore.  My plate is pretty full.  Trying to clear needinfos.

Comment 3

[Eddy Bruel [:ejpbruel]]

Thanks for the update Kannan!

Comment 4

[Sebastian Zartner [:sebo]]

Bulk changing the status, as there is no assignee anymore.

Sebastian

Comment 5

[Jason Laster [:jlast]]

closing as we have re-written the mochitests