https://bugs.kde.org/show_bug.cgi?id=430597

Hy <hymu...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |---

--- Comment #6 from Hy <hymu...@gmail.com> ---
Thanks for all the attention.

Unfortunately, this did not solve the problem. Please see below:

What I did was the following:

> uname -a
Linux hy-virtual-machine 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

and I then ran the following commands:

bunzip2 valgrind-3.16.1.tar.bz2 
tar vxf valgrind-3.16.1.tar 
cd valgrind-3.16.1/
sed -i 's|/doc/valgrind||' docs/Makefile.in 
./configure --prefix=/usr --datadir=/usr/share/doc/valgrind-3.16.1
make
sudo make install

once installed, I tried again with kstars, and it crashed again, again
mentioning syscall 315:


> valgrind --version
valgrind-3.16.1


> valgrind /usr/bin/kstars
==169940== Memcheck, a memory error detector
==169940== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==169940== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==169940== Command: /usr/bin/kstars
==169940== 
--169940-- WARNING: unhandled amd64-linux syscall: 315
--169940-- You may be able to write your own handler.
--169940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--169940-- Nevertheless we consider this a bug.  Please report
--169940-- it at http://valgrind.org/support/bug_reports.html.
==169940== 
==169940== Process terminating with default action of signal 11 (SIGSEGV)
==169940==  General Protection Fault
==169940==    at 0x1654F36D: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==169940==    by 0x165191A5: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==169940==    by 0x16519857: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==169940==    by 0x15BEB3C7: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==169940==    by 0x161EAE6B: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==169940==    by 0x15BED95B: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==169940==    by 0x1611396C: ??? (in
/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so)
==169940==    by 0x1585240C: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==169940==    by 0x1583EB98: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==169940==    by 0x1583A653: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==169940==    by 0x1583ABF1: ??? (in
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0)
==169940==    by 0x157BE5D2: ??? (in
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so)
==169940== 
==169940== HEAP SUMMARY:
==169940==     in use at exit: 5,189,403 bytes in 37,619 blocks
==169940==   total heap usage: 710,882 allocs, 673,263 frees, 42,464,872 bytes
allocated
==169940== 
==169940== LEAK SUMMARY:
==169940==    definitely lost: 0 bytes in 0 blocks
==169940==    indirectly lost: 0 bytes in 0 blocks
==169940==      possibly lost: 29,651 bytes in 464 blocks
==169940==    still reachable: 5,077,120 bytes in 36,481 blocks
==169940==                       of which reachable via heuristic:
==169940==                         length64           : 4,960 bytes in 82
blocks
==169940==                         newarray           : 2,096 bytes in 51
blocks
==169940==         suppressed: 0 bytes in 0 blocks
==169940== Rerun with --leak-check=full to see details of leaked memory
==169940== 
==169940== For lists of detected and suppressed errors, rerun with: -s
==169940== 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.

Reply via email to