Binary builds cannot step into source code for stdlib functions due to bad location info

[KristofferC]

Due to JuliaLang/julia#26314 we are getting spurious location info for functions in the stdlib:

julia> using LinearAlgebra

julia> import JuliaInterpreter.enter_call

julia> enter_call(norm, [1,2])
Frame for norm(itr) in LinearAlgebra at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.1\LinearAlgebra\src\generic.jl:448
  1 448  1 ─ %1 = (#self#)(itr, 2)
  2 448  └──      return %1
itr = [1, 2]

If not too difficult, we could perhaps detect this and rewrite the prefix to Sys.STDLIB. Best would of course be to fix it in Base but not sure how hard that is.

[pfitzseb]

Should CodeTracking handle this, maybe?

[timholy]

• Try harder to find the true path of a method  timholy/CodeTracking.jl#14
• timholy/Revise.jl@87aaecf

But this only works if the user is running Revise; there is still room for #146, though it would be better to call whereis on the method and then correct the path as needed.

[KristofferC]

#146