Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working

[Josef W. <Jos...@gm...>]

Am 02.02.2015 um 00:00 schrieb Christian Priebe:
> I'm back to the previous issue that callgrind_control or more
> specifically vgdb hangs. This is the output I get when running vgdb -d
> ...

Hmm. Then it looks like a hang in the vgdb handler in callgrind, but I
have no idea why.

Can you first check if the hang also appears with another callgrind
request such as
"vgdb --pid=XXX zero", and with another tool (e.g. none) and another vgdb
request, like "vgdb --pid=XXX v.wait 500" ?

If that works, it would be interesting to see the last lines of
Callgrind debug output
with "... --ct-verbose=2 ..." (or 3...), but warning: this can be huge,
and should be
directed to a file (eg. with --log-file=XX).

Josef