diff options
| author | Narayan Kamath <narayan@google.com> | 2017-05-24 15:07:25 +0100 |
|---|---|---|
| committer | Narayan Kamath <narayan@google.com> | 2017-05-31 10:35:32 +0100 |
| commit | a73df601b7fe192001f4b9b5ddeb17b8efe3981b (patch) | |
| tree | 268e9df211bc6e81391f8e121e9ccde25c70b26c /libunwindstack/tests/MemoryFileTest.cpp | |
| parent | 844940d751be6cf6078c9e816fc09356034c1b26 (diff) | |
tombstoned: allow intercepts for java traces.
All intercept requests and crash dump requests must now specify a
dump_type, which can be one of kDebuggerdNativeBacktrace,
kDebuggerdTombstone or kDebuggerdJavaBacktrace. Each process can have
only one outstanding intercept registered at a time.
There's only one non-trivial change in this changeset; and that is
to crash_dump. We now pass the type of dump via a command line
argument instead of inferring it from the (resent) signal, this allows
us to connect to tombstoned before we wait for the signal as the
protocol requires.
Test: debuggerd_test
Change-Id: I189b215acfecd08ac52ab29117e3465da00e3a37
Diffstat (limited to 'libunwindstack/tests/MemoryFileTest.cpp')
0 files changed, 0 insertions, 0 deletions