diff options
Diffstat (limited to 'deps/v8/src/diagnostics/gdb-jit.h')
| -rw-r--r-- | deps/v8/src/diagnostics/gdb-jit.h | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/deps/v8/src/diagnostics/gdb-jit.h b/deps/v8/src/diagnostics/gdb-jit.h index 82f5ce892c..eb4d515a81 100644 --- a/deps/v8/src/diagnostics/gdb-jit.h +++ b/deps/v8/src/diagnostics/gdb-jit.h @@ -5,6 +5,8 @@ #ifndef V8_DIAGNOSTICS_GDB_JIT_H_ #define V8_DIAGNOSTICS_GDB_JIT_H_ +#include "src/base/address-region.h" + // // GDB has two ways of interacting with JIT code. With the "JIT compilation // interface", V8 can tell GDB when it emits JIT code. Unfortunately to do so, @@ -29,9 +31,19 @@ struct JitCodeEvent; namespace internal { namespace GDBJITInterface { #ifdef ENABLE_GDB_JIT_INTERFACE + // JitCodeEventHandler that creates ELF/Mach-O objects and registers them with // GDB. void EventHandler(const v8::JitCodeEvent* event); + +// Expose some functions for unittests. These only exercise the logic to add +// AddressRegion to CodeMap, and checking for overlap. It does not touch the +// actual JITCodeEntry at all. +V8_EXPORT_PRIVATE void AddRegionForTesting(const base::AddressRegion region); +V8_EXPORT_PRIVATE void ClearCodeMapForTesting(); +V8_EXPORT_PRIVATE size_t +NumOverlapEntriesForTesting(const base::AddressRegion region); + #endif } // namespace GDBJITInterface } // namespace internal |