History log of /fuchsia/zircon/system/core/crashanalyzer/rules.mk
Revision Date Author Comments
# 88958d74 20-Sep-2018 Doug Evans <dje@google.com>

[crashlogger] Move crashlogger.h to zircon-internal

It can now be used by, eg., garnet.

Tested: compiles
Plus used crashlogger to help debug DX-448

Change-Id: I8a851f9d7292d05dd6a4f4ce42dfcf5e1fb668a4


# b1ee7841 11-Sep-2018 George Kulakowski <kulakowski@google.com>

[crash] Use the real fuchsia.mem.Buffer

Zircon has supported fidl dependencies for a while now.

ZX-2406 #comment

Test: Build, looked at a crash
Change-Id: I365a94763e28415f908b1c4be5aedce787000e23


# 8a50233e 03-Jul-2018 Adam Barth <abarth@google.com>

[fidl] Rename FIDL directories

These names more closely match what we publish in the SDK. Ideally, we'd
use . as the separator, but Zircon's build system cannot handle . in
directory names, so we use - instead.

Test: Builds.
Change-Id: Ia420a364d2accac39faebade8f3f8ed72088556a


# e33af975 05-Jun-2018 Adam Barth <abarth@google.com>

[crashanalyzer] Host crashanalyzer in svchost

Rather than having devmgr launch crashanalyzer directly, devmgr now
connects to crashanalyzer as a service hosted by svchost. This approach
will make it easier to host a crashpad-based crash analyzer in sysmgr in
the future.

Change-Id: I27afb9efb37593420c67daf4167f90627e657298


# bdd6aef7 04-Jun-2018 Scott Graham <scottmg@chromium.org>

[crash] Remove Intel PT integration from crashanalyzer

Change-Id: I6b575e0abf1bef89bff3775fd995110321253b2a


# 52e16b14 09-May-2018 Scott Graham <scottmg@chromium.org>

[debug][devmgr] Create crashsvc as system-level exception handler

crashsvc listens on the root job's exception port and dispatches to
back to devmgr to have it deal with the exception. devmgr in turn
launches an analyzer process to do something with the process that
sustained the exception. This is to allow for customization of the
exception handler, rather than always having crashlogger handle
exceptions. Short doc on rationale at go/crashsvc.

For the time being however, a refactored crashlogger (named
crashanalyzer) is still always used as the analyzer. Followups will
allow for customization of the analyzer.

crashanalyzer is a stripped down copy of crashlogger. For the time being
an #ifdef ENABLE_CRASHLOGGER is available in devmgr for easy switching
on/off, to restore the previous behaviour of registering crashlogger as
the exception handler on the root job.

Change-Id: Id10c52c2a31a5ccfeed9b63eb794559c77592df8