To Whom it may concern,
is it possible to detect all calls of some specific function in the code
with Callgrind?
Let's say I have some project and I know, that there's function SparseSolver
() used several times and I need to know where specifically (caller
function/file + line number, so I'd b
> is it possible to detect all calls of some specific function in the code with
> Callgrind?
>
> Let's say I have some project and I know, that there's function
> SparseSolver() used several times and I need to know where specifically
> (caller function/file + line number, so I'd be able to find
2016-08-30 14:41 GMT+02:00 John Reiser :
> > is it possible to detect all calls of some specific function in the code
> with Callgrind?
> >
> > Let's say I have some project and I know, that there's function
> SparseSolver() used several times and I need to know where specifically
> (caller functi
Thank you, that is a big help. I do have a follow up question. When a
Valgrind client allocates memory that will be used as a shadow copy of the
user's data, I would guess that is not included in is_valid_for_client. As an
experiment, I ORd together the results of is_valid_for_cleint and
is_
Ok - I was wrong. The problem is that is_valid_for_client is too strict. And
or'ing that with is_valid_for_valgrind is too loose. In the end, by trial and
error, I came with a test that seems to work for Daikon.
First, I check the original is_mem_defined, if that fails, then we're done.
If th
On Tue, 2016-08-30 at 10:02 -0700, Mark Roberts wrote:
> Ok - I was wrong. The problem is that is_valid_for_client is too strict.
> And or'ing that with
> is_valid_for_valgrind is too loose. In the end, by trial and error, I came
> with a test that seems to work for Daikon.
>
> First, I che
I don't think that is_valid_for_valgrind should really be required. That
delimits areas which Valgrind itself can use but the client isn't allowed
to access.
In what way is is_valid_for_client too strict?
J
--
___
We chase down pointers to find user values. Some of those pointers we
modify to point to shadow memory (we copy chunks of the stack for safe
keeping, for example) and I believe those Daikon allocated blocks are
considered Valgrind space not client space.
Mark
> -Original Message-
> From:
