breakpad

mirror of https://github.com/yuzu-emu/breakpad.git synced 2024-10-20 05:18:19 +02:00

Mirror of Google Breakpad project

Go to file

benchan@chromium.org 907f95c5bd Modify CrashGenerator::CreateChildCrash to copy proc files. This patch is taken from the downstream version of breakpad in Chromium OS: https://gerrit.chromium.org/gerrit/15148 LinuxCoreDumperTest previously assumes the proc files of the child process created by CrashGenerator::CreateChildCrash() have the same content as its parent process, which may not be true. This CL modifies CrashGenerator to copy the proc files of the child process, created by CreateChildCrash(), before crashing that process. BUG=chromium-os:25252 TEST=Verified the following: TEST=Tested the following: 1. Build on 32-bit and 64-bit Linux with gcc 4.4.3 and gcc 4.6. 2. Build on Mac OS X 10.6.8 with gcc 4.2 and clang 3.0 (with latest gmock). 3. All unit tests pass. Review URL: https://breakpad.appspot.com/353001 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@925 4c0a9323-5329-0410-9bdc-e9ce6186880e		2012-02-23 18:50:08 +00:00
autotools	ditch libtool, only build static libs	2010-10-05 19:38:51 +00:00
m4	Issue 378 - Don't compile Linux client libraries on non-Linux systems	2010-08-31 15:09:01 +00:00
src	Modify CrashGenerator::CreateChildCrash to copy proc files.	2012-02-23 18:50:08 +00:00
aclocal.m4	ditch libtool, only build static libs	2010-10-05 19:38:51 +00:00
AUTHORS	Make build system less annoying (#8 ) r=bryner	2006-08-30 20:05:05 +00:00
ChangeLog	Initial import, which includes the Windows client-side dump_syms tool, and	2006-08-25 21:14:45 +00:00
codereview.settings	Add codereview.settings so we can use gcl.	2010-06-19 02:48:54 +00:00
configure	Remove NetworkSourceLine{Resolver,Server} and related code. It never wound up being useful enough to use in production, so let's drop the maintenence burden	2011-07-07 20:53:52 +00:00
configure.ac	Remove NetworkSourceLine{Resolver,Server} and related code. It never wound up being useful enough to use in production, so let's drop the maintenence burden	2011-07-07 20:53:52 +00:00
COPYING	Relicense to BSD (#29 ). r=bryner	2006-09-20 21:16:16 +00:00
DEPS	Delete svn:executable from the DEPS file. Hans has a badly configured client on Windows?	2010-05-18 01:46:59 +00:00
INSTALL	Add logging to minidump processor (#82 ). First part: logging infrastructure	2007-05-17 18:34:37 +00:00
Makefile.am	Add partial unit tests for dwarf2reader::CompilationUnit.	2012-02-01 14:57:58 +00:00
Makefile.in	Add partial unit tests for dwarf2reader::CompilationUnit.	2012-02-01 14:57:58 +00:00
NEWS	Initial import, which includes the Windows client-side dump_syms tool, and	2006-08-25 21:14:45 +00:00
README	Update readme and fix glog properties.	2010-08-13 18:49:03 +00:00

README

Breakpad is a set of client and server components which implement a
crash-reporting system.


-----
Getting started in 32-bit mode (from trunk)
Configure: CXXFLAGS=-m32 CFLAGS=-m32 CPPFLAGS=-m32 ./configure
    Build: make
     Test: make check
  Install: make install

If you need to reconfigure your build be sure to run "make distclean" first.


-----
To request change review:
0. Get access to a read-write copy of source.
   Owners at http://code.google.com/p/google-breakpad/ are able to grant
   this access.

1. Check out a read-write copy of source using instructions at
   http://code.google.com/p/google-breakpad/source/checkout

2. Make changes. Build and test your changes.
   For core code like processor use methods above.
   For linux/mac/windows, there are test targets in each project file.

3. Download http://codereview.appspot.com/static/upload.py

4. Run upload.py from the 'src' directory:
   upload.py --server=breakpad.appspot.com

   You will be prompted for credential and a description.

5. At http://breakpad.appspot.com you'll find your issue listed; click on it,
   and select Publish+Mail, and enter in the code reviewer and CC
   google-breakpad-dev@googlegroups.com

6. When applying code review feedback, specify the '-i' option when running
   upload.py again and pass the issue number so it updates the existing issue,
   rather than creating a new one.
   Be sure to rerun upload.py from the same directory as you did for previous
   uploads to allow for proper diff calculations.