2006-11-14 (Tue) ã® 09:42 -0700 ã« Rob Savoye ããã¯æ¸ãã¾ãã: > strk wrote: > > Well, if we're taking too much memory we can't really tell > > when we'll going to run out of it. I guess a proper approach > > would be producing a diagram of where most memory goes, > > While mudflap won't print out a chart, it will tell you about every > access to see if there is a problem. Often I've seen bugs that trash the > stack create various weird errors, hiding the original problem. I also > have some code that instruments the malloc buffers in the kernel, which > can also be useful at times like this.
Unfortunately, valgrind does not support NetBSD, and as far as I know (though very few knowledge about NetBSD), NetBSD seems not to have gcc-4.x so mudflap is not useful for NetBSD only at present. Hiroyuki Ikezoe _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
