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

[Christian P. <chr...@gm...>]

2015-02-02 21:26 GMT+00:00 Philippe Waroquiers <
phi...@sk...>:

> 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 memcheck.
> >
> > > So, apparently this has nothing to do with callgrind but with valgrind
> > > (or my setup) in general.
> >
> > Ok, perhaps Philippe has an idea what's going wrong.
>
> >From the vgdb traces, it looks like all is working at vgdb side,
> and that it is the valgrind side that does not properly replies
> back to vgdb.
>
> At this stage, I do not see too much what is going wrong.
> So, let's capture some more data.
>
> On what distro/platform/... are you running ?
>

Thanks again to both of you for helping! The "experiments" are run on 64bit
Ubuntu 14.04.


>
> Can you also do the following experiments ?
>
> 1. under your user account (so no sudo, etc), do
>       # in one window:
>       valgrind sleep 100
>       # then in another window
>       vgdb --pid=xxxxxx help
>    This last help command should output the list of commands supported
>    by valgrind gdbserver
>    If that does not work (i.e. vgdb blocks), redo the same but
>    giving   -v -v -v -d -d -d    options to valgrind
>    and      -d -d -d             option  to vgdb
>    and send the traces
>

Works fine.


>
> 2. If the above works, do the same operations, but with the technique
>    you use to launch mysql
>    IIUC, use sudo in one window to launch valgrind
>    and sudo in another window to launch vgdb
>    (I am not too sure what the --user=mysql option does/means for mysqld
>     so no idea if you can really simulate what that does easily).
>
>    Again, if that does not work, redo with the -v/-d args as above
>
>
Works fine. The --user=mysql option would result in mysqld being run under
the mysql user, but I haven't used this option in any of the recent test
runs so it shouldn't matter.


> 3. If the above works, then give options  -v/-d to
>    valgrind that runs mysql
>    and to the vgdb
>
> As suggested by Josef, you might create a bug in bugzilla so as to
> attach the traces (compressed if too big) of the first failing
> experiment.
>

I created a bug report here:

https://bugs.kde.org/show_bug.cgi?id=343715

Thanks
Christian


>
> Thanks
>
> Philippe
>
>
>