On 20-mei-2007, at 17:39, Anthony Chaumas-Pellet wrote:
Hello,
I'm currently hacking away a wxhaskell program that uses up 100% CPU
even when it should be idle. So, rather than doing blind guesswork,
I've thought about using profiling to spot the zealous function. I do
not need a very
You are not missing anything obvious. The process is in fact
somewhat tricky. What you have to do is the following snip
Thanks! I've followed your instructions and got a profiler-enabled
binary up and running. I'd figured out how to modify the Makefile
(silly me searching for *G*HC), but I had
Just in case anyone was wondering how to do this with the other major
Haskell GUI lib Gtk2Hs...
./configure --enable-profiling
some day when Gtk2Hs is cabalised it'll be even easier.
Duncan
On Sun, 2007-05-20 at 17:39 +0200, Anthony Chaumas-Pellet wrote:
Hello,
I'm currently hacking away a
Hello,
I'm currently hacking away a wxhaskell program that uses up 100% CPU
even when it should be idle. So, rather than doing blind guesswork,
I've thought about using profiling to spot the zealous function. I do
not need a very accurate result, though.
ghc with -prof -auto(-all) produces the
