[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Paul Floyd changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #16 from Paul Floyd --- We can close this since there is a good workaround. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 --- Comment #15 from Hy --- Thanks Mark! Excellent find. I tried "export LIBGL_ALWAYS_SOFTWARE=1" before running valgrind, and yes it does now run. Excellent workaround. I don't know if this is a VMWare issue, though can't rule it out--e.g. I've heard of others who run non-VM ubuntu with the same issue, but I'll re-post if I find out differently. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 --- Comment #14 from Mark Wielaard --- This looks like a QT/VMWare graphics issue https://bugreports.qt.io/browse/QTBUG-69993 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 --- Comment #13 from Hy --- (In reply to Paul Floyd from comment #12) > On Fedora 33 amd64 I can run qtcreator 4.14 / Qt 5.15.2, though it does > generate vast numbers of errors which slows execution significantly. > > Could you post the end of the output when using --trace-syscalls=yes? I'll do both kstars and qtcreator for you, and am a little generous for "end of output". Here's kstars first: > valgrind --trace-syscalls=yes /usr/bin/kstars ==258094== Memcheck, a memory error detector ==258094== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==258094== Using Valgrind-3.17.0.GIT and LibVEX; rerun with -h for copyright info ==258094== Command: /usr/bin/kstars ==258094== SYSCALL[258094,1](12) sys_brk ( 0x0 ) --> [pre-success] Success(0x403) SYSCALL[258094,1](158) arch_prctl ( 12289, 1ffec0 ) --> [pre-fail] Failure(0x16) SYSCALL[258094,1](63) sys_newuname ( 0x1ffefffbc0 )[sync] --> Success(0x0) SYSCALL[258094,1](257) sys_openat ( 4294967196, 0x402f950(/usr/lib/valgrind/vgpreload_core-amd64-linux.so), 524288 ) --> [async] ... SYSCALL[258094,1](257) ... [async] --> Success(0x3) ... SYSCALL[258084,1](257) ... [async] --> Success(0x14) SYSCALL[258084,1](5) sys_newfstat ( 20, 0x1ffeff8680 )[sync] --> Success(0x0) SYSCALL[258084,1](0) sys_read ( 20, 0x11e3c0c0, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x7) SYSCALL[258084,1](3) sys_close ( 20 )[sync] --> Success(0x0) SYSCALL[258084,1](217) sys_getdents64 ( 19, 0x132983b0, 32768 ) --> [async] ... SYSCALL[258084,1](217) ... [async] --> Success(0x0) SYSCALL[258084,1](4) sys_newstat ( 0x11908598(/dev/dri/card0), 0x1ffeffe2c0 )[sync] --> Success(0x0) SYSCALL[258084,1](4) sys_newstat ( 0x119085c8(/dev/dri/renderD128), 0x1ffeffe2c0 )[sync] --> Success(0x0) SYSCALL[258084,1](3) sys_close ( 19 )[sync] --> Success(0x0) SYSCALL[258084,1](318) sys_getrandom ( 0x1ffeffeb48, 8, 1 )[sync] --> Success(0x8) SYSCALL[258084,1](257) sys_openat ( 4294967196, 0x1620e797(/usr/share/drirc.d), 591872 ) --> [async] ... SYSCALL[258084,1](257) ... [async] --> Success(0x13) SYSCALL[258084,1](5) sys_newfstat ( 19, 0x1ffeffda50 )[sync] --> Success(0x0) SYSCALL[258084,1](217) sys_getdents64 ( 19, 0x133c86a0, 32768 ) --> [async] ... SYSCALL[258084,1](217) ... [async] --> Success(0x60) SYSCALL[258084,1](217) sys_getdents64 ( 19, 0x133c86a0, 32768 ) --> [async] ... SYSCALL[258084,1](217) ... [async] --> Success(0x0) SYSCALL[258084,1](3) sys_close ( 19 )[sync] --> Success(0x0) SYSCALL[258084,1](257) sys_openat ( 4294967196, 0x1ffeffdbe0(/usr/share/drirc.d/00-mesa-defaults.conf), 0 ) --> [async] ... SYSCALL[258084,1](257) ... [async] --> Success(0x13) SYSCALL[258084,1](0) sys_read ( 19, 0x11e3af00, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x1000) SYSCALL[258084,1](318) sys_getrandom ( 0x1ffeffda68, 8, 1 )[sync] --> Success(0x8) SYSCALL[258084,1](0) sys_read ( 19, 0x1333061d, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x1000) SYSCALL[258084,1](0) sys_read ( 19, 0x1333061c, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x1000) SYSCALL[258084,1](0) sys_read ( 19, 0x13330636, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x1000) SYSCALL[258084,1](0) sys_read ( 19, 0x13330642, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x1000) SYSCALL[258084,1](0) sys_read ( 19, 0x13330616, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x1000) SYSCALL[258084,1](0) sys_read ( 19, 0x13330610, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0xb1e) SYSCALL[258084,1](0) sys_read ( 19, 0x13330610, 4096 ) --> [async] ... SYSCALL[258084,1](0) ... [async] --> Success(0x0) SYSCALL[258084,1](3) sys_close ( 19 )[sync] --> Success(0x0) SYSCALL[258084,1](257) sys_openat ( 4294967196, 0x1620e7aa(/etc/drirc), 0 ) --> [async] ... SYSCALL[258084,1](257) ... [async] --> Failure(0x2) SYSCALL[258084,1](257) sys_openat ( 4294967196, 0x1ffeffdbe0(/home/hy/.drirc), 0 ) --> [async] ... SYSCALL[258084,1](257) ... [async] --> Failure(0x2) SYSCALL[258084,1](16) sys_ioctl ( 18, 0xc0406400, 0x13441e60 ) --> [async] ... SYSCALL[258084,1](16) ... [async] --> Success(0x0) SYSCALL[258084,1](16) sys_ioctl ( 18, 0xc0406400, 0x13441e60 ) --> [async] ... SYSCALL[258084,1](16) ... [async] --> Success(0x0) SYSCALL[258084,1](5) sys_newfstat ( 18, 0x1ffeffeb90 )[sync] --> Success(0x0) SYSCALL[258084,1](72) sys_fcntl[ARG3=='arg'] ( 18, 1030, 3 )[sync] --> Success(0x13) SYSCALL[258084,1](16) sys_ioctl ( 19, 0xc0406400, 0x13444c00 ) --> [async] ... SYSCALL[258084,1](16) ... [async] --> Success(0x0) SYSCALL[258084,1](16) sys_ioctl ( 19, 0xc0406400, 0x13444c00 ) --> [async] ... SYSCALL[258084,1](16) ... [async] --> Success(0x0) SYSCALL[258084,1](16) sys_ioctl ( 19, 0xc0106440, 0x1ffeffeb20 ) --> [async] ... SYSCALL[258084,1](16) ... [async] -->
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 --- Comment #12 from Paul Floyd --- On Fedora 33 amd64 I can run qtcreator 4.14 / Qt 5.15.2, though it does generate vast numbers of errors which slows execution significantly. Could you post the end of the output when using --trace-syscalls=yes? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 --- Comment #11 from Hy --- 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.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 --- Comment #10 from Tom Hughes --- No that is your program crashing, not valgrind. I mean it might be causes by a bug in valgrind's emulation of the system but it's impossible to tell from that. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Hy changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #9 from Hy --- 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.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Mark Wielaard changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #8 from Mark Wielaard --- *** This bug has been marked as a duplicate of bug 369029 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Mark Wielaard changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Mark Wielaard --- Try the current git version of valgrind and/or a version that has that commit backported. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Hy changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #6 from Hy --- 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.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Resolution|FIXED |DUPLICATE --- Comment #5 from Mark Wielaard --- Specifically this was: commit 6323fd5bfd94c3f80e2ff44f16488e0172bd9a96 Author: Mark Wielaard Date: Mon Jul 27 16:36:17 2020 +0200 Handle linux syscalls sched_getattr and sched_setattr The only "special" thing about these syscalls is that the given struct sched_attr determines its own size for future expansion. Original fix by "ISHIKAWA,chiaki" https://bugs.kde.org/show_bug.cgi?id=369029 *** This bug has been marked as a duplicate of bug 369029 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Tom Hughes changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Tom Hughes --- As Paul says that system call has been implemented in the current release. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=430597 Tom Hughes changed: What|Removed |Added Summary|Valgrind crashes when |unhandled amd64-linux |trying to debug kstars |syscall: 315 -- You are receiving this mail because: You are watching all bug changes.
