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 ch
2015-02-02 10:42 GMT+00:00 Josef Weidendorfer :
> 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 han
Am 02.02.2015 um 12:49 schrieb Christian Priebe:
> The same line repeats until I shutdown vgdb. Ok, running "vgdb --pid=XXX
> v.wait 500" without any tool (i.e. "valgrind bin/mysqld")
Without a tool specified, the default is memcheck.
> So, apparently this has nothing to do with callgrind but wit
On Mon, 2015-02-02 at 14:51 +0100, Josef Weidendorfer wrote:
> Am 02.02.2015 um 12:49 schrieb Christian Priebe:
> > The same line repeats until I shutdown vgdb. Ok, running "vgdb --pid=XXX
> > v.wait 500" without any tool (i.e. "valgrind bin/mysqld")
>
> Without a tool specified, the default is me
2015-02-02 21:26 GMT+00:00 Philippe Waroquiers <
philippe.waroqui...@skynet.be>:
> On Mon, 2015-02-02 at 14:51 +0100, Josef Weidendorfer wrote:
> > Am 02.02.2015 um 12:49 schrieb Christian Priebe:
> > > The same line repeats until I shutdown vgdb. Ok, running "vgdb
> --pid=XXX
> > > v.wait 500" wi
