>
> >
> > On Fri, 2017-07-28 at 12:44 +0100, Frediano Ziglio wrote:
> > > Recent GitLab CI jobs are failing to run valgrind checks
> > > (like https://gitlab.com/spice/spice/-/jobs/25220999).
> > >
> > > This as recent distro changes cause valgrind not to find some
> > > symbols required to dete
>
> On Fri, 2017-07-28 at 12:44 +0100, Frediano Ziglio wrote:
> > Recent GitLab CI jobs are failing to run valgrind checks
> > (like https://gitlab.com/spice/spice/-/jobs/25220999).
> >
> > This as recent distro changes cause valgrind not to find some
> > symbols required to detect some GLib supp
On Fri, Jul 28, 2017 at 12:44:57PM +0100, Frediano Ziglio wrote:
> Recent GitLab CI jobs are failing to run valgrind checks
> (like https://gitlab.com/spice/spice/-/jobs/25220999).
>
> This as recent distro changes cause valgrind not to find some
> symbols required to detect some GLib suppression
On Fri, 2017-07-28 at 12:44 +0100, Frediano Ziglio wrote:
> Recent GitLab CI jobs are failing to run valgrind checks
> (like https://gitlab.com/spice/spice/-/jobs/25220999).
>
> This as recent distro changes cause valgrind not to find some
> symbols required to detect some GLib suppression errors.
Recent GitLab CI jobs are failing to run valgrind checks
(like https://gitlab.com/spice/spice/-/jobs/25220999).
This as recent distro changes cause valgrind not to find some
symbols required to detect some GLib suppression errors.
Adding debugging information for GLib solve the problem.
Signed-o
