Re: [Valgrind-users] Expected slowdown

[Julian S. <js...@ac...>]

> It is not easy to answer the first question. The programm is running inside
> of a nutshell and I cannot say how many live blocks the shell has when my
> application is started. The run I terminated with CTRL+C and mentioned in
> an earlier mail had 98,138,916 allocations and 97,052,020 frees. That
> indicates a number of 1,086,896 live blocks.
>
> My core application operates only on about 100-10,000 live blocks. The rest
> belongs to the nutshell.
>
> I have now started the programm with -v. What is the interessting output?

It is in fact this; I mistakenly thought it appears only at -v.  I guess
the new run with -v is pointless.

== malloc/free: 98,138,916 allocs, 97,052,020 frees, 
18,848,731,867 bytes allocated.

It all sounds like stupid questions but we're slowly accumulating
useful info.

Now I look at the annotated source you sent, and also the stuff about
the tree traversal.  And I'm thinking, are you doing very deep recursion
(I mean, function-call recursion) to process the tree(s), and at the
same time doing some mallocs/frees during that recursion?

J