On Sat, 2019-06-29 at 01:47 +0200, Mark Wielaard wrote:
> FAIL: run-large-elf-file.sh
> ===========================
> 
> long_bit: 64
> space_available: 38
> mem_available: 7
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 3.72662 s, 288 MB/s
> addsections 2 testfile38 2147483648
> add_sections 'testfile38': 2 (sec_size: 2147483648)
> setshstrndx: 10
> strip -o testfile38.strip -f testfile38.debug testfile38
> elflint --gnu testfile38.strip
> No errors
> elflint --gnu -d testfile38.debug
> No errors
> unstrip testfile38.strip testfile38.debug
> elfcmp  testfile38.strip
> addsections 2 testfile27 2147483648
> add_sections 'testfile27': 2 (sec_size: 2147483648)
> setshstrndx: 30
> strip -o testfile27.strip -f testfile27.debug testfile27
> /srv/buildbot/worker/elfutils-centos-x86_64/build/elfutils-
> 0.176/_build/src/strip: while writing 'testfile27.debug.SjHGU1': out
> of memory
> [...]
> So, this is running the test under valgrind.
> In which case we might need even more free memory available.
> 
> The test did succeed earlier on the worker, not under valgrind.

So I pushed the attached commit to just increase the amount of free
memory needed when running under valgrind.

Cheers,

Mrk