diff options
| author | Kostya Kortchinsky <kostyak@google.com> | 2021-10-07 12:29:39 -0700 |
|---|---|---|
| committer | Kostya Kortchinsky <kostyak@google.com> | 2021-10-07 14:01:58 -0700 |
| commit | 6727832c324c1fb43946275d24e2931fde94bc0d (patch) | |
| tree | 84c15d807bacc332308a34a11bae4968b6882c21 /lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h | |
| parent | 9f93f2bfbd3fedb94490d42e48b89c2a8f05ff0a (diff) | |
| download | llvm-6727832c324c1fb43946275d24e2931fde94bc0d.zip llvm-6727832c324c1fb43946275d24e2931fde94bc0d.tar.gz llvm-6727832c324c1fb43946275d24e2931fde94bc0d.tar.bz2 | |
[scudo] Reduce the scope of AllocAfterFork
`ScudoWrappersCppTest.AllocAfterFork` was failing obscurely sometimes.
Someone pointed us to Linux's `vm.max_map_count` that can be
significantly lower on some machines than others. It turned out that
on a machine with that setting set to 65530, some `ENOMEM` errors
would occur with `mmap` & `mprotect` during that specific test.
Reducing the number of times we fork, and the maximum size allocated
during that test makes it pass on those machines.
Differential Revision: https://reviews.llvm.org/D111342
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h')
0 files changed, 0 insertions, 0 deletions