https://bugs.kde.org/show_bug.cgi?id=430597
Hy <hymu...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Status|RESOLVED |REOPENED
--- Comment #9 from Hy <hymu...@gmail.com> ---
Thanks. I compiled and ran valgrind from git as follows:
git clone git://sourceware.org/git/valgrind.git
sudo apt install autoconf
cd valgrind
sh ./autogen.sh
./configure --prefix=/usr --datadir=/usr/share/doc/valgrind-3.16.1
make
sudo make install
and then once again tried to debug kstars (which does normally run without any
segv--certainly at startup it is usually stable):
However, as you can see, when I start up valgrind on kstars, this time it
doesn't mention the 315 signal, but it does exit immediately with a "general
protection fault". Is this indicating some flaw in kstars or valgrind or the
way valgrind is trying to debug kstars?
If I just run /usr/bin/kstars (without valgrind) I get the normal kstars
startup screen and skymap.
Thanks,
Hy
> /usr/bin/valgrind /usr/bin/kstars
==183751== Memcheck, a memory error detector
==183751== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==183751== Using Valgrind-3.17.0.GIT and LibVEX; rerun with -h for copyright
info
==183751== Command: /usr/bin/kstars
==183751==
==183751==
==183751== Process terminating with default action of signal 11 (SIGSEGV)
==183751== General Protection Fault
==183751== at 0x15D4E36D: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==183751== by 0x15D181A5: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==183751== by 0x15D18857: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==183751== by 0x153EA3C7: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==183751== by 0x159E9E6B: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==183751== by 0x153EC95B: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==183751== by 0x1591296C: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==183751== by 0x1505140C: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==183751== by 0x1503DB98: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==183751== by 0x15039653: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==183751== by 0x15039BF1: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==183751== by 0x14FBD5D2: ??? (in
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so)
==183751==
==183751== HEAP SUMMARY:
==183751== in use at exit: 5,188,795 bytes in 37,617 blocks
==183751== total heap usage: 710,888 allocs, 673,271 frees, 42,463,917 bytes
allocated
==183751==
==183751== LEAK SUMMARY:
==183751== definitely lost: 0 bytes in 0 blocks
==183751== indirectly lost: 0 bytes in 0 blocks
==183751== possibly lost: 29,139 bytes in 463 blocks
==183751== still reachable: 5,077,024 bytes in 36,480 blocks
==183751== of which reachable via heuristic:
==183751== length64 : 4,960 bytes in 82
blocks
==183751== newarray : 2,096 bytes in 51
blocks
==183751== suppressed: 0 bytes in 0 blocks
==183751== Rerun with --leak-check=full to see details of leaked memory
==183751==
==183751== For lists of detected and suppressed errors, rerun with: -s
==183751== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
Segmentation fault (core dumped)
>
--
You are receiving this mail because:
You are watching all bug changes.
