|author||Ludovic Guegan <firstname.lastname@example.org>||Mon Nov 23 22:58:05 2020 +0100|
|committer||Mike Frysinger <email@example.com>||Mon Nov 23 23:15:15 2020 +0000|
core_handler: coredump handler to produce minidump On Linux, it is possible to register a core handler via /proc/sys/kernel/core_pattern. Doing so invokes the core handler when a process crash. The core_handler uses /proc/<pid>/mem to access the process memory. This way it is not necessary to process the full coredump which takes time and consumes memory. In order to profit from this core handler, for example, one can integrate dump_syms into Yocto and generate an archive with the breakpad symbols of all the binaries in the rootfs. Minidumps are especially useful on embedded systems since they are lightweight and provide contextual information. Change-Id: I9298d81159029cefb81c915831db54884310ad05 Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2536917 Reviewed-by: Mike Frysinger <firstname.lastname@example.org>
Breakpad is a set of client and server components which implement a crash-reporting system.
First, download depot_tools and ensure that they’re in your
Create a new directory for checking out the source code (it must be named breakpad).
mkdir breakpad && cd breakpad
fetch tool from depot_tools to download all the source repos.
fetch breakpad cd src
Build the source.
./configure && make
You can also cd to another directory and run configure from there to build outside the source tree.
This will build the processor tools (
src/processor/minidump_dump, etc), and when building on Linux it will also build the client libraries and some tools (
Optionally, run tests.
Optionally, install the built libraries
If you need to reconfigure your build be sure to run
make distclean first.
To update an existing checkout to a newer revision, you can
git pull as usual, but then you should run
gclient sync to ensure that the dependent repos are up-to-date.
Follow the steps above to get the source and build it.
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.
Commit your changes to your local repo and upload them to the server. http://dev.chromium.org/developers/contributing-code e.g.
git commit ... && git cl upload ... You will be prompted for credential and a description.
At https://chromium-review.googlesource.com/ you'll find your issue listed; click on it, then “Add reviewer”, and enter in the code reviewer. Depending on your settings, you may not see an email, but the reviewer has been notified with email@example.com always CC’d.