summaryrefslogtreecommitdiff
path: root/buildlib
diff options
context:
space:
mode:
authorHeitor R. Alves de Siqueira <halves@canonical.com>2019-02-08 13:05:18 +0100
committerJulian Andres Klode <julian.klode@canonical.com>2019-02-08 13:05:18 +0100
commit22e3f5d3e311bc001a05803fcf39036f620b1d96 (patch)
tree92e111713b6c2deb0375f86d295aaa5767a45b7a /buildlib
parent5d07bad6105eb1b7c158c502fe89803e120be064 (diff)
backport "do not segfault in cache generation on mmap failure"
Original commit message: Out of memory and similar circumstanzas could cause MMap::Map to fail and especially the mmap/malloc calls in it. With some additional checking we can avoid segfaults and similar in such situations – at least in theory as if this is a real out of memory everything we do to handle the error could just as well run into a memory problem as well… But at least in theory (if MMap::Map is made to fail always) we can deal with it so good that a user actually never sees a failure (as the cache it tries to load with it fails and is discarded, so that DynamicMMap takes over and a new one is build) instead of segfaulting. Closes: 803417 LP: #1815129
Diffstat (limited to 'buildlib')
0 files changed, 0 insertions, 0 deletions