File: README.md

package info (click to toggle)
chromium 141.0.7390.107-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 6,246,132 kB
  • sloc: cpp: 35,264,965; ansic: 7,169,920; javascript: 4,250,185; python: 1,460,635; asm: 950,788; xml: 751,751; pascal: 187,972; sh: 89,459; perl: 88,691; objc: 79,953; sql: 53,924; cs: 44,622; fortran: 24,137; makefile: 22,313; tcl: 15,277; php: 14,018; yacc: 8,995; ruby: 7,553; awk: 3,720; lisp: 3,096; lex: 1,330; ada: 727; jsp: 228; sed: 36
file content (25 lines) | stat: -rw-r--r-- 1,292 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# Allocation Recorder
The allocation_recorder lets Crashpad include a log of recent calls to malloc()
and free() when a memory safety fault is detected. Each entry includes a portion
of the stack trace as well as the size and the address of the object. The code
that generates the log lives in base/debug/allocation_trace.h

## Code organization
The component is split up into multiple parts.
 - **crash_client**: To be used by the client, that is the process for which
   a crash report shall be created. The client also contains the definition of
   the recorder.
 - **crash_handler**: To be used by the crashpad handler. In case of a crash, the
   crash handler is responsible to create a proper report from the recorder data.
   *This will be implemented in a follow up CL.*
 - **internal**: Code that is shared between crash_client and crash_handler but
   used only internally, i.e. name of the crashpad annotation used to store
   data.

## Current state of implementation
Due to the size of implementation, the feature will be implemented in multiple
CLs.

| Nr | CL | Description |
| -- | -- | ----------- |
| 1  | https://chromium-review.googlesource.com/c/chromium/src/+/4323818 | **crash_client**:  Introduce the crash client. The client should be fully implemented afterwards. |