| > valgrind to profile execuction at a lower level http://valgrind.org. | > Something like this | > | > valgrind --tool=cachegrind <prog> <args> | > [ creates a file like cachegrind.out.23915] | > cg_annotate --23915 | > [ use the correct number, of course ] | | Does that help track down allocation? If so, how?
It tells you where the program counter spends its time. Then you eye-ball the corresponding Core or STG code to see where the allocation is. It's not difficult in practice, once you get in the swing of it. Simon _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
