这是我在valgrind崩溃并停止分析我的应用程序时收到的消息:
==16317==
==16317== Valgrind's memory management: out of memory:
==16317== newSuperblock's request for 4194304 bytes failed.
==16317== 3013349376 bytes have already been allocated.
==16317== Valgrind cannot continue. Sorry.
==16317==
==16317== There are several possible reasons for this.
==16317== - You have some kind of memory limit in place. Look at the
==16317== output of 'ulimit -a'. Is there a limit on the size of
==16317== virtual memory or address space?
==16317== - You have run out of swap space.
==16317== - Valgrind has a bug. If you think this is the case or you are
==16317== not sure, please let us know and we'll try to fix it.
==16317== Please note that programs can take substantially more memory than
==16317== normal when running under Valgrind tools, eg. up to twice or
==16317== more, depending on the tool. On a 64-bit machine, Valgrind
==16317== should be able to make use of up 32GB memory. On a 32-bit
==16317== machine, Valgrind should be able to use all the memory available
==16317== to a single process, up to 4GB if that's how you have your
==16317== kernel configured. Most 32-bit Linux setups allow a maximum of
==16317== 3GB per process.
==16317==
==16317== Whatever the reason, Valgrind cannot continue. Sorry.
我尝试过使用大量交换文件,但效果并不好。 崩溃发生在我的交换文件几乎已满之前很久。 我正在使用Fedora 19。 有没有人知道这件事?我想我在互联网上读到了一个过程如何限制单个进程可以分配的内存。如果是这种情况,我可以在哪里设置它?至少给我一个很好的选择对valgrind人:P。
提前致谢
答案 0 :(得分:0)
“大多数32位Linux设置允许每个进程最多3GB。”
你已经分配了3013349376个字节,非常接近3GB。所以你可能有一个32位操作系统,而你只是为一个进程耗尽内存(其他~200兆就可能是valgrind开销)