mksnapshot for android is nondeterministic |
||||
Issue descriptionmksnapshot produces different results each time it is run: $ fetch android $ mkdir out/gn_Release_android $ gn gen --args='target_os="android" use_goma=true is_debug=false' out/gn_Release_android $ ninja -C out/gn_Release_android snapshot_blob.bin -j 1000 -v ninja: Entering directory `out/gn_Release_android' [1/1] python ../../v8/tools/run.py ./clang_x86_v8_arm/mksnapshot --startup_src gen/v8/snapshot.cc --random-seed 314159265 --startup_blob snapshot_blob.bin $ sha1sum out/gn_Release_android/snapshot_blob.bin 3a72d1625946d7d72af16509cddde35d9a050478 out/gn_Release_android/snapshot_blob.bin $ rm out/gn_Release_android/snapshot_blob.bin $ ninja -C out/gn_Release_android snapshot_blob.bin -j 1000 -v $ sha1sum out/gn_Release_android/snapshot_blob.bin 6d993830187b2f991661a8d236b0a09e117c342b out/gn_Release_android/snapshot_blob.bin
,
Jul 25 2016
,
Jul 25 2016
(moved back here). This is caused by ASLR. Prepending mksnapshot with `setarch `uname -m` solves the issue.
,
Jul 25 2016
*setarch `uname -m` -R
,
Jul 25 2016
,
Jul 25 2016
Back to https://bugs.chromium.org/p/v8/issues/detail?id=5233 again, since the fix will be in v8.
,
Jul 25 2016
,
Jul 26 2016
This has been fixed on the v8 side. |
||||
►
Sign in to add a comment |
||||
Comment 1 by stip@chromium.org
, Jul 25 2016