2018-03-26 09:43:06 +00:00
|
|
|
# Copyright 2018 the V8 project authors. All rights reserved.
|
|
|
|
|
# Use of this source code is governed by a BSD-style license that can be
|
|
|
|
|
# found in the LICENSE file.
|
|
|
|
|
|
|
|
|
|
import("../../gni/v8.gni")
|
|
|
|
|
|
|
|
|
|
group("v8_run_gcmole") {
|
|
|
|
|
testonly = true
|
|
|
|
|
|
|
|
|
|
data = [
|
|
|
|
|
"gccause.lua",
|
2019-08-29 14:37:43 +00:00
|
|
|
"GCMOLE.gn",
|
2018-03-26 09:43:06 +00:00
|
|
|
"gcmole.lua",
|
2019-09-06 15:22:37 +00:00
|
|
|
"gcmole-test.cc",
|
2018-03-26 09:43:06 +00:00
|
|
|
"gcmole-tools/",
|
|
|
|
|
"parallel.py",
|
|
|
|
|
"run-gcmole.py",
|
2019-08-29 14:37:43 +00:00
|
|
|
"suspects.whitelist",
|
2020-06-22 08:08:01 +00:00
|
|
|
"ignored_files",
|
2019-08-29 14:37:43 +00:00
|
|
|
"test-expectations.txt",
|
2018-03-26 09:43:06 +00:00
|
|
|
|
|
|
|
|
# The following contains all relevant source and build files.
|
Reland "Add postmortem debugging helper library"
This is a reland of 517ab73fd7e3fdb70220b9699bca4c69a32e212e
Updates since original: now compressed pointers passed to the function
GetObjectProperties are required to be sign-extended. Previously, the
function allowed zero-extended values, but that led to ambiguity on
pointers like 0x88044919: is it compressed or is the heap range actually
centered on 0x100000000?
Original change's description:
> Add postmortem debugging helper library
>
> This change begins to implement the functionality described in
> https://docs.google.com/document/d/1evHnb1uLlSbvHAAsmOXyc25x3uh1DjgNa8u1RHvwVhk/edit#
> for investigating V8 state in crash dumps.
>
> This change adds a new library, v8_debug_helper, for providing platform-
> agnostic assistance with postmortem debugging. This library can be used
> by extensions built for debuggers such as WinDbg or lldb. Its public API
> is described by debug-helper.h; currently the only method it exposes is
> GetObjectProperties, but we'd like to add more functionality over time.
> The API surface is restricted to plain C-style structs and pointers, so
> that it's easy to link from a debugger extension built with a different
> toolchain.
>
> This change also adds a new cctest file to exercise some basic
> interaction with the new library.
>
> The API function GetObjectProperties takes an object pointer (which
> could be compressed, or weak, or a SMI), and returns a string
> description of the object and a list of properties the object contains.
> For now, the list of properties is entirely based on Torque object
> definitions, but we expect to add custom properties in future updates so
> that it can be easier to make sense of complex data structures such as
> dictionaries.
>
> GetObjectProperties does several things that are intended to generate
> somewhat useful results even in cases where memory may be corrupt or
> unavailable:
> - The caller may optionally provide a type string which will be used if
> the memory for the object's Map is inaccessible.
> - All object pointers are compared against the list of known objects
> generated by mkgrokdump. The caller may optionally provide the
> pointers for the first pages of various heap spaces, to avoid spurious
> matches. If those pointers are not provided, then any matches are
> prefixed with "maybe" in the resulting description string, such as
> "maybe UndefinedValue (0x4288000341 <Oddball>)".
>
> Bug: v8:9376
>
> Change-Id: Iebf3cc2dea3133c7811bcefcdf38d9458b02fded
> Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1628012
> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
> Reviewed-by: Yang Guo <yangguo@chromium.org>
> Reviewed-by: Michael Stanton <mvstanton@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#62882}
Bug: v8:9376
Change-Id: I866a1cc9d4c34bfe10c7b98462451fe69763cf3f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1717090
Reviewed-by: Michael Achenbach <machenbach@chromium.org>
Reviewed-by: Michael Stanton <mvstanton@chromium.org>
Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#63008}
2019-07-30 14:38:15 +00:00
|
|
|
"../debug_helper/debug-helper.h",
|
2018-03-26 09:43:06 +00:00
|
|
|
"../../BUILD.gn",
|
|
|
|
|
"../../base/",
|
|
|
|
|
"../../include/",
|
|
|
|
|
"../../src/",
|
|
|
|
|
"../../test/cctest/",
|
Reland "[turboassembler] Introduce hard-abort mode"
This is a reland of a462a7854a081f4f34bb4c112ee33f3d69efa309
Original change's description:
> [turboassembler] Introduce hard-abort mode
>
> For checks and assertions (mostly for debug code, like stack alignment
> or zero extension), we had two modes: Emit a call to the {Abort}
> runtime function (the default), and emit a debug break (used for
> testing, enabled via --trap-on-abort).
> In wasm, where we cannot just call a runtime function because code must
> be isolate independent, we always used the trap-on-abort behaviour.
> This causes problems for our fuzzers, which do not catch SIGTRAP, and
> hence do not detect debug code failures.
>
> This CL introduces a third mode ("hard abort"), which calls a C
> function via {ExternalReference}. The C function still outputs the
> abort reason, but does not print the stack trace. It then aborts via
> "OS::Abort", just like the runtime function.
> This will allow fuzzers to detect the crash and even find a nice error
> message.
>
> Even though this looks like a lot of code churn, it is actually not.
> Most added lines are new tests, and other changes are minimal.
>
> R=mstarzinger@chromium.org
>
> Bug: chromium:863799
> Change-Id: I77c58ff72db552d49014614436259ccfb49ba87b
> Reviewed-on: https://chromium-review.googlesource.com/1142163
> Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#54592}
Bug: chromium:863799
Change-Id: I7729a47b4823a982a8e201df36520aa2b6ef5326
Reviewed-on: https://chromium-review.googlesource.com/1146100
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54656}
2018-07-24 14:12:47 +00:00
|
|
|
"../../test/common/",
|
2018-03-26 09:43:06 +00:00
|
|
|
"../../testing/gtest/include/gtest/gtest_prod.h",
|
|
|
|
|
"../../third_party/googletest/src/googletest/include/gtest/gtest_prod.h",
|
|
|
|
|
"../../third_party/icu/source/",
|
2019-05-08 11:29:40 +00:00
|
|
|
"../../third_party/wasm-api/wasm.h",
|
|
|
|
|
"../../third_party/wasm-api/wasm.hh",
|
2019-11-25 15:29:12 +00:00
|
|
|
"../../third_party/zlib/",
|
2019-06-28 08:30:09 +00:00
|
|
|
"../../third_party/inspector_protocol/",
|
2018-06-05 16:03:05 +00:00
|
|
|
"$target_gen_dir/../../",
|
2018-05-04 13:18:37 +00:00
|
|
|
"$target_gen_dir/../../torque-generated/",
|
2018-04-16 09:24:22 +00:00
|
|
|
]
|
|
|
|
|
|
2020-06-22 08:08:01 +00:00
|
|
|
deps = [ "../../:run_torque" ]
|
2018-03-26 09:43:06 +00:00
|
|
|
|
|
|
|
|
if (v8_gcmole) {
|
|
|
|
|
# This assumes gcmole tools have been fetched by a hook
|
|
|
|
|
# into v8/tools/gcmole/gcmole_tools.
|
|
|
|
|
data += [ "gcmole-tools/" ]
|
|
|
|
|
}
|
|
|
|
|
}
|
