New issue
Advanced search Search tips

Issue 662853 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

x86 N devices are not generating microdumps

Project Member Reported by tobiasjs@chromium.org, Nov 7 2016

Issue description

Library namespacing means that dlopening libnativebridge fails, and so we don't install a signal handler.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Nov 8 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2c944c9e76acc4e22a67bff89e33afd2342db0a1

commit 2c944c9e76acc4e22a67bff89e33afd2342db0a1
Author: tobiasjs <tobiasjs@chromium.org>
Date: Tue Nov 08 21:10:09 2016

Always install the microdump signal handler on N+ devices.

N+ shared library namespacing means that the current detection code that
determines whether it is safe to install the microdump signal handler
fails, because it is impossible to dlopen libnativebridge (because it
isn't in the NDK).

Because the libnativebridge on N+ devices is sufficiently recent as to
not need the test, we simply short-circuit on those devices.

BUG= 662853 

Review-Url: https://codereview.chromium.org/2483203002
Cr-Commit-Position: refs/heads/master@{#430713}

[modify] https://crrev.com/2c944c9e76acc4e22a67bff89e33afd2342db0a1/android_webview/crash_reporter/aw_microdump_crash_reporter.cc
[modify] https://crrev.com/2c944c9e76acc4e22a67bff89e33afd2342db0a1/base/android/build_info.h

Status: Fixed (was: Available)

Sign in to add a comment