Comment #3 on issue 2885 by [email protected]: mksnapshot's output isn't
deterministic
http://code.google.com/p/v8/issues/detail?id=2885
I like deterministic builds. mksnapshot is the only part of Chromium
Framework's many inputs that doesn't build deterministically. (Having said
that, it doesn't cause obvious problems in practice.)
Adding --random-seed sounds easy enough.
For ASLR, could mksnapshot handle this somehow? It could check which random
load address it got, and maybe grow a --assume-load-address parameter?
(Since Chrome is built with ASLR too, that wouldn't be the actual load
address though.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
