|
From: Philippe W. <phi...@sk...> - 2014-07-08 23:20:19
|
On Tue, 2014-07-08 at 16:14 -0400, Eliot Moss wrote: > On 7/8/2014 3:47 PM, Karl Cronburg wrote: > > On 07/08/2014 02:48 PM, Philippe Waroquiers wrote: > >> On Tue, 2014-07-08 at 14:39 -0400, Eliot Moss wrote: > >>> On 7/8/2014 2:04 PM, Philippe Waroquiers wrote: > >>>> On Tue, 2014-07-08 at 03:49 -0400, Karl Cronburg wrote: > > > We're interested in using malloc/free client requests to see if we can > > get memcheck to tell us when the garbage collector is handling its' > > own memory incorrectly. > > That sounds like a radical change to Jikes RVM. At present it > doesn't really use malloc/free. It mmaps big chunks and manages > them all itself, both for the system (i.e., outside of the garbage > collected universe) and for the GC'ed heap. Valgrind has client requests that can be used to describe "user managed pool". These are a.o. used to run "valgrind in valgrind", so as to find valgrind bugs with itself. These requests are supposed to be general enough to describe most "user defined" memory pools Philippe |