-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Internal error: No such method: 'uriPathToNative', url 'file:///tmp/tmpQxaBII/pkg/compiler/implementation/dart2js.dart' #6233
Comments
Thanks for the report! Set owner to @kasperl. |
How are you running dart2js? I cannot reproduce this (not even with the SDK from revision 13851). Lowering priority until we have an indication that this is still a problem. Removed Priority-Critical label. |
It looks a bit fishy that your dart2js.dart file is in a temporary directory. |
This comment was originally written by domi...@google.com The same way that I have been running dart2js this whole time: It's run I'm running 'ant generate-JS' from the master branch of dartbox2d.
|
This comment was originally written by domi...@google.com Running dart2js directly, instead of through ant, I get the same issue: $ $DART_SDK/bin/dart2js -o example/benchmarks/BenchmarkRunner.dart.js example/benchmarks/BenchmarkRunner.dart #0 NoSuchMethodErrorImplementation._throwNew (dart:core-patch:247:3) |
Do you have any idea where file:///tmp/tmpQxaBII/ stems from? Does this happen no matter what you try to compile? You can also try running dart2js without the wrapper script in SDK/bin/dart2js by doing something ala: SDK/bin/dart SDK/pkg/compiler/implementation/dart2js.dart hello.dart where hello.dart is the simplest piece of code you can think of. Also be aware that you cannot have a space between -o and the file name; see issue #3379. |
This comment was originally written by domi...@google.com Running directly works without error. I have no idea where the /tmp folder is coming from. Once the process ends, that folder does not exist. I also noted 'Using snapshot ~/sdk/dart-sdk.13851/bin/../pkg/compiler/implementation/dart2js.dart.snapshot' which I haven't noticed before. When I run through the dart VM directly, I don't get any output about a snapshot being used. Relevant? |
This comment was originally written by @austincummings I have the same problem. I just downloaded sdk revision 13851. I'm just using the shell script to run it. Using snapshot /home/austin/lib/dart-sdk/bin/../pkg/compiler/implementation/dart2js.dart.snapshot #0 NoSuchMethodErrorImplementation._throwNew (dart:core-patch:247:3) |
This comment was originally written by @austincummings I was able to compile using the wrapper script by removing '$SNAPSHOT' from line 26 in $DART_SDK/bin/dart2js. Before: After: |
I think the tmp file names is a side-effect of the SDK build process. With a more recent version, it should be something like file:///long_buildbot_path/out/ReleaseIA32/dart-sdk.tmp/... We should report a bug with the VM team about this: the snapshot should use the file names given on the command line, otherwise, why give them? But this is not relevant for this bug report. I think this is a problem with snapshots. |
Assuming AustinCummings95 is reporting the same problem, I'll take a look at SDK revision 13851. cc @kasperl. |
I cannot reproduce the problem and I need the following information: Revision (see the file revision in the root of the Dart SDK). OS name and version? 32 or 64 bit? Added NeedsInfo label. |
This comment was originally written by @austincummings Revision: 13851 |
I can reproduce. It might be an issue with the 64-bit version of Dart. Added Accepted label. |
This is looking like a build problem. If I try to build the SDK for Linux x64, I run into a compilation with V8. This means that I cannot create 64-bit version of the SDK. I think I remember that we may have hacked around that by taking the IA32 version of the SDK and copy the x64 version of the into the IA32 SDK. This probably was a great short-term solution, but now we have a snapshot that was generated with IA32 version of the VM being loaded by the x64 version of the VM. Clearly, that doesn't work. I see two options:
dgrove: can you shed some light on the x64 SDK build process? cc @ricowind. |
I'm currently trying option 1 in this CL: https://codereview.chromium.org/11301019 |
Peter, we do currently create the 64 bit SDK using the 32 bit one. See dart/editor/build/build.py, line 901 or so. It's not an ideal solution but it did get us unblocked. |
I have confirmed this is a problem with the build process of the 64-bit SDK. Set owner to @devoncarew. |
This issue was originally filed by domi...@google.com
Running dart2js from SDK revision 13851 gives the following:
Internal error: No such method: 'uriPathToNative', url 'file:///tmp/tmpQxaBII/pkg/compiler/implementation/dart2js.dart' line 248Using snapshot dart-sdk/bin/../pkg/compiler/implementation/dart2js.dart.snapshot
[exec] pos 7
[exec] var root = uriPathToNative("/$LIBRARY_ROOT");
[exec]
[exec] #0 NoSuchMethodErrorImplementation._throwNew (dart:core-patch:247:3)
[exec] #1 compilerMain (file:///tmp/tmpQxaBII/pkg/compiler/implementation/dart2js.dart:248:7)
[exec] #2 main (file:///tmp/tmpQxaBII/pkg/compiler/implementation/dart2js.dart:278:7)
revision 13679 was fine.
The text was updated successfully, but these errors were encountered: