From: Ferenc Wagner [mailto:[EMAIL PROTECTED]]
...
One more question: is there a way not to truncate the call
stacks? Ie in the hp file I see lines like
(144)showData2/showData/ma... 12
and I'd like to see showData2/showData/main or so.
hear, hear...
I'm also having some fun with
something interesting turned up again. Setting cut=8 in
Show2.hs and running it with ./show +RTS -h -i0.01 gives
show: fatal error: main thread has been GC'd
It may be silly, since 0.01 1/50, but this error message
isn't too helpful. Btw, +RTS -? says:
-imsec Time between
Simon Marlow [EMAIL PROTECTED] writes:
Both of these bugs were fixed in 5.04.2.
Great.
I'm afraid there's no way at the moment, but I'll look
into adding a flag. The problem is that the longer the
stacks get, the less room there is for the graph - hp2ps
tends to squeeze the graph up to
Hello,
something interesting turned up again. Setting cut=8 in
Show2.hs and running it with ./show +RTS -h -i0.01 gives
show: fatal error: main thread has been GC'd
It may be silly, since 0.01 1/50, but this error message
isn't too helpful. Btw, +RTS -? says:
-imsec
With 5.04 I get almost the same, look:
COST CENTREMODULE %time %alloc
showData1 Main 87.1 89.2
ncEps Epsilon3.63.4
cutAbove4 Tcsa
Hello,
Please help me understanding GHC 5.02.2 profiling output!
Here is the root of my program (Show.hs):
\begin{code}
showData:: BaseVector a = Params - Operator a - String
showData params pot = unlines [Version 3.1,
