Summary: 
  Here's a little patch that allows a little finer user control over 
  what information gets dumped when asking about memory statistics.

Motivation: 
  In tracking down memory leaks in my program, or gnome, or gtk, etc.,
  often all I care about is the total amount used. Since I may have to
  make extensive calls to get the summary information having the one
  line instead of the 30 or so speeds things up and facilitates my
  ability to scan the output looking for problems.

Implimentation details:

In the patch, I added a single new function:

void     g_mem_summarize (const gchar *msg, gboolean show_alloc_size, 
			  gboolean show_large_alloc, gboolean show_alloc,
			  gboolean show_freed, gboolean show_used);

which has booleans for each of the pieces of the output for the
existing routine, g_mem_profile(void). g_mem_profile then is just a
call to this new routine which setts all of the parameters to
TRUE. 

Another possible interface would be to have just one parameter which
is interpreted as bit vector. One would also have to define a bunch of
bitmasks to allow each of the pieces analogous to be used. This is
similar say to the way the C lib 2 open() routine works with O_APPEND,
O_CREAT and so on.

R. Bernstein
rocky@panix.com