[wrapper-tracing] Fix write barrier test
The test was manually hooking up a wrapper in a non-supported way. Switch to using the providing bindings methods. This was flushed out when incremental marking started scanning roots right after the test and encountered a broken leftover object. Bug: chromium:757440 Change-Id: I0636c48a22d88f2d85ded1ebab2732d3ef6de077 Reviewed-on: https://chromium-review.googlesource.com/997795Reviewed-by:Kentaro Hara <haraken@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#548581}
Showing
Please register or sign in to comment