|
From: Per H. <ph...@op...> - 2004-10-27 15:10:40
|
Would it be possible to add a feature to limit the size of the heap that the program running in valgrind can use (as allocated by the various memory functions)? The reason for this featurerequest is that it's somewhat hard to use ulimit when running programs in valgrind, but it would still be useful to simulate low-memory systems when testing if your program is out-of-memory safe. -- Per Hedbor |
|
From: Dennis L. <pla...@gm...> - 2004-10-27 23:06:09
|
At 17:10 27.10.2004, you wrote: >Would it be possible to add a feature to limit the size of the heap that >the program running in valgrind can use (as allocated by the various >memory functions)? > >The reason for this featurerequest is that it's somewhat hard to use >ulimit when running programs in valgrind, but it would still be useful to >simulate low-memory systems when testing if your program is out-of-memory >safe. Thats a great Idea, I posted it too a few months ago, but with no positive reply. In a previous post it was said that supporting memory ulimits is a non-goal, so it would be nice if develeopers can say if supporting valgrind internal memory limits is a goal or not, so we can look for a tool that supports it or wait until valgrind supports it... (I could really use such an option for debugging a tool that behaves strangely when running on an embedded linux with only 32MB ...) greets Dennis Carpe quod tibi datum est |
|
From: Nicholas N. <nj...@ca...> - 2004-10-28 08:28:32
|
On Thu, 28 Oct 2004, Dennis Lubert wrote: >> Would it be possible to add a feature to limit the size of the heap that >> the program running in valgrind can use (as allocated by the various >> memory functions)? >> >> The reason for this featurerequest is that it's somewhat hard to use >> ulimit when running programs in valgrind, but it would still be useful to >> simulate low-memory systems when testing if your program is out-of-memory >> safe. > > Thats a great Idea, I posted it too a few months ago, but with no positive > reply. In a previous post it was said that supporting memory ulimits is a > non-goal, so it would be nice if develeopers can say if supporting valgrind > internal memory limits is a goal or not, so we can look for a tool that > supports it or wait until valgrind supports it... (I could really use such an > option for debugging a tool that behaves strangely when running on an > embedded linux with only 32MB ...) The desired limit would just be on the heap, not on other used memory too? N |
|
From: Dennis L. <pla...@gm...> - 2004-10-28 10:30:54
|
At 10:28 28.10.2004, you wrote: >On Thu, 28 Oct 2004, Dennis Lubert wrote: >> supports it or wait until valgrind supports it... (I could really use >> such an option for debugging a tool that behaves strangely when running >> on an embedded linux with only 32MB ...) > >The desired limit would just be on the heap, not on other used memory too? For my part, yes. Amount of stack memory used is unimportant to me at the moment. I would even be ok with only the memory limited which my program allocates, not counting the memory that would normally be used for glibc,pthread etc. (all of what valgrind emulates with its own code) for its internal use.... dont know how valgrind would implement it.. greets Dennis Carpe quod tibi datum est |