From: Stephen Kellett Date: 2005-07-20T07:10:55+09:00 Subject: Re: Memory profiling? In message , Cameron McBride writes >I suspected there might >be underlying nastiness when you mentioned binary patching, but being >ignorant of many important details it was a guess and I wanted to >excluded the possibility of some other constraint (silly GUI or >something). Well, my experience of fixing Memory problems for people extends back to the beta of Purify on Solaris in 90/91. That was text only back then. Things have moved on. You may regard the GUI interfaces on such data as silly, but from my perspective (and those of our customers) they are essential, as the requests for "can we have such and such a display" indicate. Memory problems tend to benefit from advanced GUIs and search/interrogate features even more than profiling/coverage/flow tracing. Deadlock/thread analysis also seems to benefit more. >In any case, I'd really love the ability to memory profile ruby code. >I've found it difficult to do with the ad hoc methods I've utilized. If you haven't got hooks into the VM the info you have is thoroughly misleading (regardless of OS). Stephen -- Stephen Kellett Object Media Limited http://www.objmedia.demon.co.uk/software.html Computer Consultancy, Software Development Windows C++, Java, Assembler, Performance Analysis, Troubleshooting