v8/test/mkgrokdump
Dominik Inführ d4c1da341a [heap] Remove Heap::map_space_ field and MapSpace class
Bug: v8:12578
Change-Id: I724164405cf3ba6d433655fa0fde5b9986fe04a0
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3959661
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Auto-Submit: Dominik Inführ <dinfuehr@chromium.org>
Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#83786}
2022-10-19 08:04:27 +00:00
..
BUILD.gn [build] Fold v8_wrappers into v8_libbase 2021-02-25 10:56:20 +00:00
DEPS
mkgrokdump.cc [heap] Remove Heap::map_space_ field and MapSpace class 2022-10-19 08:04:27 +00:00
mkgrokdump.status [sandbox] Skip mkgrokdump test in non-sandbox mode 2022-09-08 21:42:16 +00:00
README [sandbox] Update test/mkgrokdump/README 2022-09-14 17:09:49 +00:00
testcfg.py [test] Refactor testrunner (4) 2022-07-18 09:52:24 +00:00

If you change the heap layout, expect this test to fail (in CQ). You will then
need to build x64 release with v8_enable_sandbox=true and run
`<outdir>/mkgrokdump > tools/v8heapconst.py` to rebaseline.
The V8 sandbox has to be manually enabled as it is enabled by default only for
Chromium builds, but not standalone v8 builds.