[Valgrind-users] Re: =?iso-8859-1?Q?Re:_Re:_[Valgrind-users]_Re:_Re:_Re:_[Valgrind-users]_valgrind_dies_with_assertion_on_start-up?=

[Nicholas N. <nj...@ca...>]

On Tue, 31 Aug 2004 oli...@on... wrote:

>> What kernel/distro are you running?  I just learnt of a RH8.0 system that
>> was having the same problem.  The fix there was to increase the amount of
>> swap space to 1.9GB.
>>
>> This is apparently necessary because the kernel doesn't seem to support
>> allocate-on-write mmaps, and so swap space must be bigger than any
>> individual mapped segment;  and Memcheck uses a 1.5GB segment.
>>
>> So, if you are able to increase the amount of swap on that machine, this
>> might fix the problem.  If you do try this, can you please let us know if
>> it works or not?  Thanks.
>
> The machine is running a Red Hat 8 with kernel 2.4.18. Unfortunately I
> can't increase the swap space, because I am already very low on space,
> but I use 512MB so far. Another machine with the same system and 1.5GB
> swap space can run it fine. So I guess that seems to fix it.

Great, thanks for the data point.

We are, slowly but surely, working out how to improve Valgrind's memory 
layout.  So these problems people are having will eventually be fixed... 
thanks for your patience in the meantime.

N