Fix README.ANDROID + formatting

This patch updates README.ANDROID, since the client library
now supports directly generating a minidump without raising
a signal, and that it builds and runs fine on Android/x86.

+ Formatting fixes in minidump_writer_unittest.cc
Review URL: https://breakpad.appspot.com/446002

git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1026 4c0a9323-5329-0410-9bdc-e9ce6186880e
This commit is contained in:
digit@chromium.org 2012-09-05 08:08:53 +00:00
parent 343ce73b73
commit f792eecd1e
2 changed files with 4 additions and 9 deletions

View file

@ -5,13 +5,8 @@ This document explains how to use the Google Breakpad client library
on Android, and later generate valid stack traces from the minidumps on Android, and later generate valid stack traces from the minidumps
it generates. it generates.
Note that this release only supports ARM-based Android systems. This release supports ARM and x86 based Android systems. MIPS is not
We're working on adding support for x86 and MIPS, but that might currently supported by Breakpad.
require an udpated NDK release.
IMPORTANT: Currently, Minidump generation only works when a signal is
handled by Breakpad. I.e. calling WriteMinidump() directly
at runtime will not work.
I. Building the client library: I. Building the client library:
=============================== ===============================

View file

@ -329,7 +329,7 @@ TEST(MinidumpWriterTest, DeletedBinary) {
// Copy binary to a temp file. // Copy binary to a temp file.
AutoTempDir temp_dir; AutoTempDir temp_dir;
string binpath = temp_dir.path() + "/linux-dumper-unittest-helper"; string binpath = temp_dir.path() + "/linux-dumper-unittest-helper";
ASSERT_EQ(true, CopyFile(helper_path.c_str(), binpath.c_str())) \ ASSERT_TRUE(CopyFile(helper_path.c_str(), binpath.c_str()))
<< "Failed to copy " << helper_path << " to " << binpath; << "Failed to copy " << helper_path << " to " << binpath;
ASSERT_EQ(0, chmod(binpath.c_str(), 0755)); ASSERT_EQ(0, chmod(binpath.c_str(), 0755));