commit | c670c537f41105185f7cfcd6d3dc09f1c41a1097 | [log] [tgz] |
---|---|---|
author | keith_miller@apple.com <keith_miller@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Thu Jun 29 17:34:57 2017 +0000 |
committer | keith_miller@apple.com <keith_miller@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Thu Jun 29 17:34:57 2017 +0000 |
tree | d78207487566e3139a7d8f2a873f042b10b71e0d | |
parent | 31b51b41193a5d10e42431b3a1b150e9b71ac86e [diff] |
VMTraps has some races https://bugs.webkit.org/show_bug.cgi?id=173941 Reviewed by Michael Saboff. Source/JavaScriptCore: This patch refactors much of the VMTraps API. On the message sending side: 1) No longer uses the Yarr JIT check to determine if we are in RegExp code. That was unsound because RegExp JIT code can be run on compilation threads. Instead it looks at the current frame's code block slot and checks if it is valid, which is the same as what it did for JIT code previously. 2) Only have one signal sender thread, previously, there could be many at once, which caused some data races. Additionally, the signal sender thread is an automatic thread so it will deallocate itself when not in use. On the VMTraps breakpoint side: 1) We now have a true mapping of if we hit a breakpoint instead of a JIT assertion. So the exception handler won't eat JIT assertions anymore. 2) It jettisons all CodeBlocks that have VMTraps breakpoints on them instead of every CodeBlock on the stack. This both prevents us from hitting stale VMTraps breakpoints and also doesn't OSR codeblocks that otherwise don't need to be jettisoned. 3) The old exception handler could theoretically fail for a couple of reasons then resume execution with a clobbered instruction set. This patch will kill the program if the exception handler would fail. This patch also refactors some of the jsc.cpp functions to take the CommandLine options object instead of individual options. Also, there is a new command line option that makes exceptions due to watchdog timeouts an acceptable result. * API/tests/testapi.c: (main): * bytecode/CodeBlock.cpp: (JSC::CodeBlock::installVMTrapBreakpoints): * dfg/DFGCommonData.cpp: (JSC::DFG::pcCodeBlockMap): (JSC::DFG::CommonData::invalidate): (JSC::DFG::CommonData::~CommonData): (JSC::DFG::CommonData::installVMTrapBreakpoints): (JSC::DFG::codeBlockForVMTrapPC): * dfg/DFGCommonData.h: * jsc.cpp: (functionDollarAgentStart): (checkUncaughtException): (checkException): (runWithOptions): (printUsageStatement): (CommandLine::parseArguments): (jscmain): (runWithScripts): Deleted. * runtime/JSLock.cpp: (JSC::JSLock::didAcquireLock): * runtime/VMTraps.cpp: (JSC::sanitizedTopCallFrame): (JSC::VMTraps::tryInstallTrapBreakpoints): (JSC::VMTraps::willDestroyVM): (JSC::VMTraps::fireTrap): (JSC::VMTraps::handleTraps): (JSC::VMTraps::VMTraps): (JSC::VMTraps::~VMTraps): (JSC::findActiveVMAndStackBounds): Deleted. (JSC::installSignalHandler): Deleted. (JSC::VMTraps::addSignalSender): Deleted. (JSC::VMTraps::removeSignalSender): Deleted. (JSC::VMTraps::SignalSender::willDestroyVM): Deleted. (JSC::VMTraps::SignalSender::send): Deleted. * runtime/VMTraps.h: (JSC::VMTraps::~VMTraps): Deleted. (JSC::VMTraps::SignalSender::SignalSender): Deleted. Tools: Add new testing mode for testing the Watchdog with our stress tests. * Scripts/run-jsc-stress-tests: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@218936 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
Downloading Safari Technology Preview to test the latest version of WebKit.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git://git.webkit.org/WebKit.git WebKit
If you want to be able to commit changes to the repository, or just want to check out branches that aren’t contained in WebKit.git, you will need track WebKit's Subversion repository. You can run the following command to configure this and other options of the new Git clone for WebKit development.
Tools/Scripts/webkit-patch setup-git-clone
For information about this, and other aspects of using Git with WebKit, read the wiki page.
Run the following command to check out WebKit's subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within WebKit.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
The first time after you install a new Xcode, you will need to run the following command to enable Xcode to build command line tools for iOS Simulator:
sudo Tools/Scripts/configure-xcode-for-ios-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for iOS:
Tools/Scripts/build-webkit --debug --ios-simulator.
Install the dependencies by running the following command:
Tools/gtk/install-dependencies
Then run the following command to build additional dependencies:
Tools/Scripts/update-webkitgtk-libs
Run the following command to build WebKit with debugging symbols for GTK+ port:
Tools/Scripts/build-webkit --debug --gtk
Note that the procedure for building a release tarball is different. For more information, see the wiki page.
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.