valgrind and kstars

Hy Murveit murveit at gmail.com
Mon Dec 21 20:14:34 GMT 2020


I was frustrated that I could not try to debug KStars memory issues using
valgrind. When I ran, e.g.  'valgrind /usr/bin/kstars' I would get an
uninformative crash very soon and the program (valgrind) would die.

I've run this on an Ubuntu 20.04 VM on macbook, but I believe I've heard
from others that they also could not run valgrind on KStars (please correct
me if I'm wrong).

I opened a bug on the valgrind bug tracking system,
https://bugs.kde.org/show_bug.cgi?id=430597 and happily it came to a
reasonable conclusion.

(a) I found that, not just KStars, but all Qt programs seemed to crash with
valgrind, and
(b) There is a workaround!
On the command line, before starting KStars, run:

export LIBGL_ALWAYS_SOFTWARE=1

Then, on the command line start up valgrind with kstars, e.g.

valgrind ~/Projects/kstars-build/kstars/kstars


Hy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20201221/59747c9f/attachment.htm>


More information about the Kstars-devel mailing list