aboutsummaryrefslogtreecommitdiff
path: root/src/third_party/libdisasm/ia32_settings.h
diff options
context:
space:
mode:
authorprimiano@chromium.org <primiano@chromium.org>2014-10-28 16:45:14 +0000
committerprimiano@chromium.org <primiano@chromium.org>2014-10-28 16:45:14 +0000
commit507a09f4de7e4c9881135c427353a40dab410c5a (patch)
treedc9561f724ba35a31c74e88b23fc5c85d6105dd1 /src/third_party/libdisasm/ia32_settings.h
parentFix breakpad on mips and x86_64 for the NDK r10c update. (diff)
downloadbreakpad-507a09f4de7e4c9881135c427353a40dab410c5a.tar.xz
Introduce microdump writer class.
Microdumps are a very lightweight variant of minidumps. They are meant to dump a minimal crash report on the system log (logcat on Android), containing only the state of the crashing thread. This is to deal with cases where the user has opted out from crash uploading but we still want to generate meaningful information on the device to pull a stacktrace for development purposes. Conversely to conventional stack traces (e.g. the one generated by Android's debuggerd or Chromium's base::stacktrace) microdumps do NOT require unwind tables to be present in the target binary. This allows to save precious binary size (~1.5 MB for Chrome on Arm, ~10 MB on arm64). More information and design doc on crbug.com/410294 BUG=chromium:410294 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1398 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'src/third_party/libdisasm/ia32_settings.h')
0 files changed, 0 insertions, 0 deletions