Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 580828 - dev-util/valgrind-3.11.0 tracing weston: --4849:0: aspacem Valgrind: FATAL: aspacem assertion failed: ! is_freeslot(ix)
Summary: dev-util/valgrind-3.11.0 tracing weston: --4849:0: aspacem Valgrind: FATAL: a...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Anthony Basile
Depends on:
Reported: 2016-04-22 13:07 UTC by Pekka Paalanen
Modified: 2016-04-27 14:28 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
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:

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.