Bug 167802
| Summary: | Support -v / --version in `jsc` binary | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mathias Bynens <mathias> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | fpizlo, ggaren, jfbastien, keith_miller, mathias, saam, ysuzuki |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Mathias Bynens
There is currently no way to figure out the version of a given `jsc` binary:
```
$ jsc -v
Could not open file: -v
$ jsc --version
ERROR: invalid option: --version
>>> ^D
$ jsc --help
Usage: jsc [options] [files] [-- arguments]
-d Dumps bytecode (debug builds only)
-e Evaluate argument as script code
-f Specifies a source file (deprecated)
-h|--help Prints this help message
-i Enables interactive mode (default if no files are specified)
-m Execute as a module
-s Installs signal handlers that exit on a crash (Unix platforms only)
-p <file> Outputs profiling data to a file
-x Output exit code before terminating
--sample Collects and outputs sampling profiler data
--test262-async Check that some script calls the print function with the string 'Test262:AsyncTestComplete'
--strict-file=<file> Parse the given file as if it were in strict mode (this option may be passed more than once)
--module-file=<file> Parse and evaluate the given file as module (this option may be passed more than once)
--exception=<name> Check the last script exits with an uncaught exception with the specified name
--options Dumps all JSC VM options and exits
--dumpOptions Dumps all non-default JSC VM options before continuing
--<jsc VM option>=<value> Sets the specified JSC VM option
```
Please consider making `-v` / `--version` (and possibly `-h` / `--help`) output something useful.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Yusuke Suzuki
I'm not sure whether JavaScriptCore has some `version`.
Mathias Bynens
(In reply to comment #1)
> I'm not sure whether JavaScriptCore has some `version`.
Anything — even a build number, revision number, or commit hash — would be better than nothing.