[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-21 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=430597 Paul Floyd changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-21 Thread Hy
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

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-21 Thread Mark Wielaard
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

2020-12-21 Thread Hy
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 out

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Paul Floyd
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? --

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Hy
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

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Tom Hughes
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 watchi

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Hy
https://bugs.kde.org/show_bug.cgi?id=430597 Hy changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPEN

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=430597 Mark Wielaard changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #8 from Mark Wielaard --

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=430597 Mark Wielaard changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Hy
https://bugs.kde.org/show_bug.cgi?id=430597 Hy changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=430597 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Resolution|FIXED

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=430597 Tom Hughes changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 430597] unhandled amd64-linux syscall: 315

2020-12-20 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=430597 Tom Hughes changed: What|Removed |Added Summary|Valgrind crashes when |unhandled amd64-linux |trying to