[dev_compiler] Some locations are missing from the source map

[annagrin]

Some locations are missing from the source map, causing stack frames being displayed on a wrong line in Chrome DevTools or Dart DevTools.

Repro

In the following example, pause at the breakpoint and step into the call, then click on a frame that calls the top frame.

void main() {
    printObjectMultiLine();
}

void printObjectMultiLine() {
  print( // Breakpoint
    createEnclosingObject()
      ..initialize(),
  );
}

MyClass createEnclosingObject() {
  return EnclosingClass();
}

class MyClass {
  MyClass();

  void initialize() {}
}

Expected

Debugger is pointing at line stating at the createObject

Actual

Debugger is pointing at line stating at the print

Details

Note the locations that are printed (by adding debug print in dwds) when trying to hover over a variable in the second from the top frame. There seem to be no location in source map for createObject().

JavaScript call stack in chrome devtools (line 198 corresponds to 197 in the printout above)

[annagrin]

Another example: step a few times into runApp call in a flutter app (such as a counter app, for example):

Looks like the location for void scheduleWarmUpFrame() { is missing so we end up showing location for a previous function instead when chrome stopped on the following line below:

[annagrin]

Another example:

Step once into runApp, see incorrect line shown in dart instead of pointing at the beginning of WidgetsFlutterBinding.ensureInitialized()