Bug 580828

Summary:	dev-util/valgrind-3.11.0 tracing weston: --4849:0: aspacem Valgrind: FATAL: aspacem assertion failed: ! is_freeslot(ix)
Product:	Gentoo Linux	Reporter:	Pekka Paalanen <pq>
Component:	Current packages	Assignee:	Anthony Basile <blueness>
Status:	RESOLVED OBSOLETE
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
URL:	https://bugzilla.redhat.com/show_bug.cgi?id=1283774
Whiteboard:
Package list:		Runtime testing required:	---

Description Pekka Paalanen 2016-04-22 13:07:48 UTC

This is the same issue as reported to Fedora in the referred URL. Running Weston in Valgrind fails Valgrind itself, not only Weston.

I hear Fedora fixed this using the patch here:
http://pkgs.fedoraproject.org/cgit/rpms/valgrind.git/tree/valgrind-3.11.0-aspacemgr.patch

According to the comments in the patch, you should be able to find the patch already merged upstream, so this is essentially just waiting for an upstream fix release. If you want, you could patch 3.11 in Gentoo too.


Reproducible: Always

Steps to Reproduce:
1. Be in X, open an X terminal to run from.
2. Execute: $ valgrind -v weston

Actual Results:  
Weston starts to launch, creates an X11 window, and then Valgrind crashes with:
--4849:0: aspacem Valgrind: FATAL: aspacem assertion failed:
--4849:0: aspacem   ! is_freeslot(ix)
--4849:0: aspacem   at m_aspacemgr/aspacemgr-segnames.c:223 (get_refcount)


Expected Results:  
Valgrind to not fail assert.


My Weston is hand-built from source, upstream master branch. I would expect the failure to also occur on the packaged version. I have Intel graphics.