History log of /system/core/debuggerd/tombstoned/tombstoned_client.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
a73df601b7fe192001f4b9b5ddeb17b8efe3981b 24-May-2017 Narayan Kamath <narayan@google.com> 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
/system/core/debuggerd/tombstoned/tombstoned_client.cpp
2d377cd6888775fe682e49a1ac34a3a6feb78708 10-May-2017 Narayan Kamath <narayan@google.com> tombstoned: Add a shared library version of libtombstoned_client...

.. for ART and the frameworks to link against. In the new stack dumping
scheme (see related bug), the Java runtime will communicate with
tombstoned in order to obtain a FD to which it can write its traces.

Also move things around to separate headers that are private
implementation details from headers that constitute the public debuggerd
API. There are currently only three such headers :

- tombstoned/tombstoned.h
- debuggerd/client.h
- debuggerd/handler.h

Bug: 32064548
Test: make

Change-Id: If1b8578550e373d84828b180bbe585f1088d1aa3
/system/core/debuggerd/tombstoned/tombstoned_client.cpp