diff options
| author | primiano@chromium.org <primiano@chromium.org> | 2015-03-10 20:06:04 +0000 |
|---|---|---|
| committer | primiano@chromium.org <primiano@chromium.org> | 2015-03-10 20:06:04 +0000 |
| commit | 9208fbc22400cca23358ce5daf66a09497e04ffe (patch) | |
| tree | 5d756c91eea6d29477032733bfb402b0618ab3e5 /src/client/linux/dump_writer_common | |
| parent | Fix Windows dump_syms x64 linking (diff) | |
| download | breakpad-9208fbc22400cca23358ce5daf66a09497e04ffe.tar.xz | |
Microdump writer: stop using new/malloc in compromised context
A recent change in the client-side microdump write (r1404) ended up
introducing a call to new() to instantiate the line buffer that
microdump uses to dump its lines. new/malloc is a luxury we cannot
afford in a compromised context.
This change switches the line buffer to be backed by the dumper
page allocator, which on Linux/Android ends up requesting pages
via mmap.
Also, the microdump write bails out without crashing if the page
allocator failed (crash during severe OOM).
BUG=640
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1432 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'src/client/linux/dump_writer_common')
0 files changed, 0 insertions, 0 deletions