<div class="gmail_quote">On Thu, Feb 5, 2009 at 3:01 PM, YC <<a href="mailto:yinso.chen@gmail.com">yinso.chen@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="gmail_quote"><div class="Ih2E3d">On Thu, Feb 5, 2009 at 2:32 PM, Jay McCarthy <<a href="mailto:jay.mccarthy@gmail.com" target="_blank">jay.mccarthy@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Yes, dump-memory-stats is what I mean. When you compile with backtracing, you'll get additional options from dms. </blockquote></div><div> Thanks Jay - is there a way for me to tell whether I have compiled with the backtracing or not? </div></div></blockquote><div> Now it's clear my built does not have backtrace enabled as I got a compilation error - anyone seen this error before? I am on centos 5.1. ./newgc.c:1271: warning: dereferencing type-punned pointer will break strict-aliasing rules In file included from ./newgc.c:1789,                  from ./gc2.c:15: ./backtrace.c: In function 'print_out_pointer': ./backtrace.c:48: warning: implicit declaration of function 'find_page' ./backtrace.c:48: warning: assignment makes pointer from integer without a cast ./backtrace.c: In function 'print_traced_objects': ./backtrace.c:97: error: 'avoid_collection' undeclared (first use in this function) ./backtrace.c:97: error: (Each undeclared identifier is reported only once ./backtrace.c:97: error: for each function it appears in.) make[4]: *** [gc2.o] Error 1 make[4]: Leaving directory `/home/yc/tmp/plt-4.1.3/src/mzscheme/gc2' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/yc/tmp/plt-4.1.3/src/mzscheme/gc2' make[2]: *** [3m] Error 2 make[2]: Leaving directory `/home/yc/tmp/plt-4.1.3/src/mzscheme' make[1]: *** [3m] Error 2 make[1]: Leaving directory `/home/yc/tmp/plt-4.1.3/src' make: *** [all] Error 2 Thanks, yc </div></div>