[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 93673] New: request for memory limits
From:       Dennis Lubert <plasmahh () tzi ! de>
Date:       2004-11-21 17:18:22
Message-ID: 20041121181820.93673.plasmahh () tzi ! de
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
        
http://bugs.kde.org/show_bug.cgi?id=93673        
           Summary: request for memory limits
           Product: valgrind
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: jseward acm org
        ReportedBy: plasmahh tzi de


When testing programs that will run on e.g. embedded systems with low memory, I
use setting memory ulimits so that the program behaves similar as on the real
system in low memory conditions. Since valgrind has a quite big memory overhead,
one cannot really use it on the embedded system, but since using ulimit is not
possible with valgrind its bad to simulate these conditions. So it would be nice
if valgrind would have some memory limit options. Im thinking of some option in
MB that limits the amount of memory that the program requests via malloc/new
etc.. Stack usage should be uncritical, although for completeness, and if its
easy to implement would be nice too...
[prev in list] [next in list] [prev in thread] [next in thread]