https://bugs.kde.org/show_bug.cgi?id=430597
--- Comment #11 from Hy <hymu...@gmail.com> --- Thanks Tom. As I said, the program doesn't crash like that normally (without valgrind), it is just starting up the gui, not doing much. On a whim, I thought, perhaps this happens with all Qt programs, not just KStars. So, I tried valgrind on QtCreator, and it crashed there too. So, this really has nothing to do with KStars. (see below for the stderr) I tried it on a small Qt program I wrote. Same segv. Seems pretty clear that valgrind and Qt don't play well together. Would you like me to open a bug that says something like Qt and Valgrind don't work together, or can you move my original bug to that? Is there something further you can advise me to do, or can you look into the Valgrind/Qt interaction, or should I just abandon trying to use valgrind for Qt programs? BTW, for sanity's sake, I also tried 'valgrind /usr/bin/emacs', and that didn't crash! Thanks for your efforts with this, Hy > valgrind /usr/bin/qtcreator ==202922== Memcheck, a memory error detector ==202922== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==202922== Using Valgrind-3.17.0.GIT and LibVEX; rerun with -h for copyright info ==202922== Command: /usr/bin/qtcreator ==202922== ==202922== ==202922== Process terminating with default action of signal 11 (SIGSEGV) ==202922== General Protection Fault ==202922== at 0x1247A36D: ??? (in /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so) ==202922== by 0x124441A5: ??? (in /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so) ==202922== by 0x12444857: ??? (in /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so) ==202922== by 0x11B163C7: ??? (in /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so) ==202922== by 0x12115E6B: ??? (in /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so) ==202922== by 0x11B1895B: ??? (in /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so) ==202922== by 0x1203E96C: ??? (in /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so) ==202922== by 0x1178440C: ??? (in /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0) ==202922== by 0x11770B98: ??? (in /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0) ==202922== by 0x1176C895: ??? (in /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0) ==202922== by 0x1176E057: ??? (in /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0) ==202922== by 0x72D6D6C: glXChooseFBConfig (in /usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0) ==202922== ==202922== HEAP SUMMARY: ==202922== in use at exit: 3,792,683 bytes in 26,239 blocks ==202922== total heap usage: 663,026 allocs, 636,787 frees, 37,548,946 bytes allocated ==202922== ==202922== LEAK SUMMARY: ==202922== definitely lost: 0 bytes in 0 blocks ==202922== indirectly lost: 0 bytes in 0 blocks ==202922== possibly lost: 28,755 bytes in 463 blocks ==202922== still reachable: 3,681,296 bytes in 25,102 blocks ==202922== of which reachable via heuristic: ==202922== length64 : 4,960 bytes in 82 blocks ==202922== newarray : 2,096 bytes in 51 blocks ==202922== suppressed: 0 bytes in 0 blocks ==202922== Rerun with --leak-check=full to see details of leaked memory ==202922== ==202922== For lists of detected and suppressed errors, rerun with: -s ==202922== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Segmentation fault (core dumped) > -- You are receiving this mail because: You are watching all bug changes.
