[valgrind] [Bug 487439] SIGILL in JDK11, JDK17
https://bugs.kde.org/show_bug.cgi?id=487439 --- Comment #11 from Paul Floyd --- That doesn't work with clang unfortunately and I have to resort to the byte array. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Keywords||regression Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487439] SIGILL in JDK11, JDK17
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #9 from Paul Floyd ---
Bill Torpey, could you build Valgrind to test a fix?
This change seems to fix your problem:
diff --git a/VEX/priv/guest_amd64_toIR.c b/VEX/priv/guest_amd64_toIR.c
index f0b1c5516..28c37f092 100644
--- a/VEX/priv/guest_amd64_toIR.c
+++ b/VEX/priv/guest_amd64_toIR.c
@@ -14138,7 +14138,7 @@ Long dis_ESC_0F__SSE2 ( Bool* decode_OK,
goto decode_success;
}
/* 66 0F 73 /6 ib = PSLLQ by immediate */
- if (have66noF2noF3(pfx) && sz == 2
+ if (have66noF2noF3(pfx) && (sz == 2 || /* ignore redundant REX.W */ sz
== 8)
&& epartIsReg(getUChar(delta))
&& gregLO3ofRM(getUChar(delta)) == 6) {
delta = dis_SSE_shiftE_imm( pfx, delta, "psllq", Iop_ShlN64x2 );
Mark, do you know how to force using rex.W in assembler?
This testcase also seems to work
/* with redundant rex.W */
static void psllq_4(void)
{
reg128_t arg1 = { .uq = { 0x0123456789abcdefULL, 0x0123456789abcdefULL } };
reg128_t result0;
char state[108];
if (sigsetjmp(catchpoint, 1) == 0)
{
asm(
"ffree %%st(7)\n"
"ffree %%st(6)\n"
"ffree %%st(5)\n"
"ffree %%st(4)\n"
"movlps %2, %%xmm1\n"
"movhps %3, %%xmm1\n"
//".rex.W psllq $12, %%xmm1\n"
".byte 0x66,0x48,0x0f,0x73,0xf1,0x0c\n"
"movlps %%xmm1, %0\n"
"movhps %%xmm1, %1\n"
"cld\n"
: "=m" (result0.uq[0]), "=m" (result0.uq[1])
: "m" (arg1.uq[0]), "m" (arg1.uq[1]), "m" (state[0])
: "xmm1"
);
if (result0.uq[0] == 0x3456789abcdef000ULL && result0.uq[1] ==
0x3456789abcdef000ULL )
{
printf("psllq_4 ... ok\n");
}
else
{
printf("psllq_4 ... not ok\n");
printf(" result0.uq[0] = %llu (expected %llu)\n", result0.uq[0],
0x3456789abcdef000ULL);
printf(" result0.uq[1] = %llu (expected %llu)\n", result0.uq[1],
0x3456789abcdef000ULL);
}
}
else
{
printf("psllq_4 ... failed\n");
}
return;
}
but it doesn't fit in with the gen_insn_test.pl script.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 453044] gbserver_tests failures in aarch64
https://bugs.kde.org/show_bug.cgi?id=453044 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Paul Floyd --- commit 790abdf7d3f3df0c968605b68ca765310689b7ce (HEAD -> master, origin/master, origin/HEAD) Author: Jesus Checa Date: Sat May 25 12:40:30 2024 +0200 Bug 453044 - gbserver_tests failures in aarch64 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461541] Add new plugin to integrate GFPGAN for face restoration.
https://bugs.kde.org/show_bug.cgi?id=461541 Jean Paul Eby changed: What|Removed |Added CC||jp...@orange.fr --- Comment #2 from Jean Paul Eby --- Thank you very much for this information ! Best regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452281] Application Windows moving randomly from screen to screen and sometimes to other desktops
https://bugs.kde.org/show_bug.cgi?id=452281 --- Comment #9 from Paul Hands --- (In reply to Zamundaaa from comment #8) > 5.27 had some of it, but sort of incomplete and a bit buggy. It should be > fully functional and auto-tested in 6.0.5 Thanks again. I'm on 6.04, so I'll await 6.,05, and let you know if it's fixed for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452281] Application Windows moving randomly from screen to screen and sometimes to other desktops
https://bugs.kde.org/show_bug.cgi?id=452281 --- Comment #7 from Paul Hands --- Thanks, Zamundaaa. What version of kwin should I look out for? -- You are receiving this mail because: You are watching all bug changes.
[plasma-redshift-control] [Bug 487487] Flickering and flickering graphical glitches when night light is active (Wayland / AMD)
https://bugs.kde.org/show_bug.cgi?id=487487 Paul Elliott changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Paul Elliott --- Quite likely another duplicate of https://bugs.kde.org/show_bug.cgi?id=480799 Apologies, quite why this did not show up in searches BEFORE I created the bug, I'm not sure. *** This bug has been marked as a duplicate of bug 480799 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480799] Artifacts/flickering when toggling night light when using two monitors
https://bugs.kde.org/show_bug.cgi?id=480799 Paul Elliott changed: What|Removed |Added CC||p...@niburu.org --- Comment #20 from Paul Elliott --- *** Bug 487487 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-redshift-control] [Bug 487487] New: Flickering and flickering graphical glitches when night light is active (Wayland / AMD)
https://bugs.kde.org/show_bug.cgi?id=487487 Bug ID: 487487 Summary: Flickering and flickering graphical glitches when night light is active (Wayland / AMD) Classification: Plasma Product: plasma-redshift-control Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: p...@niburu.org Target Milestone: --- SUMMARY With AMD gfx under Wayland, I see a lot of flickering and flickering graphical glitches when night light is on (I can easily reproduce this just by moving the slider for night light temperature. When night light is disabled I don't see any such issues. STEPS TO REPRODUCE 1. Adjust the night light colour slider towards the red end 2. Observe flickering and glitches on the desktop 3. OBSERVED RESULT Flickering and occasional flickering graphical glitches. Everything goes away with nightlight off EXPECTED RESULT Night light without flicker ;) SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-3-MANJARO (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT (Dual Monitors) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #4 from Paul Floyd --- Do you still have this problem? If so could you attach the unfiltered log file? Run perl tests/vg_regtest --keep-unfiltered memcheck/tests/linux/stack_changes and then attach stack_changes.stderr.out.unfiltered.out I'll try it on FreeBSD - reading the commit comments, it's only Darwin that doesn't work with this test. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487439] SIGILL in JDK11, JDK17
https://bugs.kde.org/show_bug.cgi?id=487439 --- Comment #7 from Paul Floyd --- That's not unusual. There may be some kind of runtime instruction set selection based on hwcaps/cpuid. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487439] SIGILL in JDK11, JDK17
https://bugs.kde.org/show_bug.cgi?id=487439 --- Comment #5 from Paul Floyd --- This looks like 66 48 0f 73 f1 0c rex.W psllq xmm1,0xc Some more from the log vex amd64->IR: unhandled instruction bytes: 0x66 0x48 0xF 0x73 0xF1 0xC 0x66 0xF 0x70 0xF5 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 "psllq" should be handled, but it looks like it's the REX prefix that is causing the problem. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487453] New: Discover doesn't see/use the new /etc/apt/ubuntu.sources file, or any .sources files in /etc/apt/sources.list.d and doesn't present the Software Sources access button
https://bugs.kde.org/show_bug.cgi?id=487453 Bug ID: 487453 Summary: Discover doesn't see/use the new /etc/apt/ubuntu.sources file, or any .sources files in /etc/apt/sources.list.d and doesn't present the Software Sources access button Classification: Applications Product: Discover Version: 5.27.11 Platform: Kubuntu OS: Other Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: sno...@icloud.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Ubuntu Software Sources content and access button missing in Discover STEPS TO REPRODUCE 1. In Kubuntu 24.04 LTS launch Discover 2. Click on Settings 3. There is no content for Ubuntus repositories that are contained in /etc/apt/ubuntu.sources 4. The Software Sources access button isn't present OBSERVED RESULT Content of /etc/apt/ubuntu.sources isn't displayed by Discover and Software Sources access button is missing EXPECTED RESULT Content of /etc/apt/ubuntu.sources should be displayed and the Software Sources access button should be present SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.27.11 (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I've confirmed this issue by renaming /etc/apt/sources.list.distUpgrade to /etc/apt/sources.list and launching Discover. Then Ubuntu Software Sources content and the Software Sources access button are presented. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487439] SIGILL in JDK11, JDK17
https://bugs.kde.org/show_bug.cgi?id=487439 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- Do you have any Valgrind logs? The Java logs are meaningless to me, other than SIGILL. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487418] [arm64] Cleanup M{SR,RS} instructions
https://bugs.kde.org/show_bug.cgi?id=487418 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487418] New: [arm64] Cleanup M{SR,RS} instructions
https://bugs.kde.org/show_bug.cgi?id=487418
Bug ID: 487418
Summary: [arm64] Cleanup M{SR,RS} instructions
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: FreeBSD
Status: REPORTED
Severity: major
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: pjfl...@wanadoo.fr
Target Milestone: ---
Partly related to https://bugs.kde.org/show_bug.cgi?id=487413
Mostly based on suggestions from Peter Maydell
1. Break up the instruction decode. At the moment, mainly because support has
been added piecemeal, there is no structure to the if blocks handling these
instructions.
That would mean having something like
if (INSN(31, 20) == BITS12(1,1,0,1,0,1,0,1,0,0,1,1))
and then breaking down instructions based on op0/op1/op2/crn/crm.
See
https://developer.arm.com/documentation/ddi0602/2024-03/Base-Instructions/MRS--Move-System-Register-to-general-purpose-register-?lang=en
2. Add checks for HWCAP or similar before decoding.
For example, sha512
3. Make feature tests open-coded rather than hard-coded.
For example, arm64g_dirtyhelper_MRS_ID_AA64PFR0_EL1 has a hard coded check
for half-precision floating-point.
This will break if future ARM architectures extend AdvSIMD to have values
higher than 1.
4. Use macros to extract and mask fields.
5. Use names to access fields
For both of the above, see m_machine.c
For instance arm64g_dirtyhelper_MRS_ID_AA64ISAR0_EL1 currently contains
w &= 0xF000F0FF;
that woule be more readable as
MASK_FIELDS(w, MAKE_MASK_FIELD(ID_AA64ISAR0_AES_SHIFT) |
MAKE_MASK_FIELD(ID_AA64ISAR0_SHA1_SHIFT) |
etc.
6. Use the value of arm64_cache_block_size read in get_cache_info rather than
using a dirty helper.
Also respect the DZP bit when decoding DC ZVA.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 487410] disInstr(arm64): unhandled instruction 0x88E1FC02
https://bugs.kde.org/show_bug.cgi?id=487410 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487410] disInstr(arm64): unhandled instruction 0x88E1FC02
https://bugs.kde.org/show_bug.cgi?id=487410 Paul Floyd changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- Please use a version of Valgrind that is more recent. 3.14 is old. I believe that the CAS instruction that you have a problem with was added in Valgrind 3.16.1. Can you please confirm that it works with a recent more Valgrind? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487413] [arm64] Unhandled M{SR,RS} instructions
https://bugs.kde.org/show_bug.cgi?id=487413
Paul Floyd changed:
What|Removed |Added
Summary|[arm64] Unhandled M{SR,RS} |[arm64] Unhandled M{SR,RS}
|instructions and cleanup|instructions
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 487413] [arm64] Unhandled M{SR,RS} instructions and cleanup
https://bugs.kde.org/show_bug.cgi?id=487413 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487413] New: [arm64] Unhandled M{SR, RS} instructions and cleanup
https://bugs.kde.org/show_bug.cgi?id=487413
Bug ID: 487413
Summary: [arm64] Unhandled M{SR,RS} instructions and cleanup
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: FreeBSD
Status: REPORTED
Severity: major
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: pjfl...@wanadoo.fr
Target Milestone: ---
https://bugs.kde.org/show_bug.cgi?id=392146 covered most of the system
registers, but there are still some unimplemented.
Unimplemented instructions common to both Linux and FreeBSD
S3_0_C0_C4_3
id_aa64zfr0_el1 (SVE Feature ID register)
id_aa64smfr0_el1 (SME Feature ID Register)
S3_0_C0_C4_6
S3_0_C0_C4_7
S3_0_C0_C5_2
S3_0_C0_C5_7
id_aa64isar2_el1 (Instruction Set Attribute Register)
S3_0_C0_C6_3
S3_0_C0_C6_4
S3_0_C0_C6_5
S3_0_C0_C6_6
S3_0_C0_C6_7
S3_0_C0_C7_3/ID_AA64MMFR3_EL1 (Memory Model Feature Register)
S3_0_C0_C7_4/ID_AA64MMFR4_EL1 (Memory Model Feature Register)
On FreeBSD the unimplemented instructions are
S3_0_C0_C7_5
S3_0_C0_C7_6
S3_0_C0_C7_7
cntpct_el0 (Counter-timer Physical Count register)
On Linux the unimplemented instructions are
id_isar0_el1
id_isar1_el1
id_isar2_el1
id_isar3_el1
id_isar4_el1
id_isar5_el1
id_mmfr4_el1
S3_0_C0_C2_7/id_isar6_el1
mvfr0_el1
mvfr1_el1
mvfr2_el1
S3_0_C0_C3_3
S3_0_C0_C3_4/id_pfr2_el1
S3_0_C0_C3_5/id_dfr1_el1
S3_0_C0_C3_6/id_mmfr5_el1
S3_0_C0_C3_7
id_aa64zfr0_el1
id_aa64smfr0_el1
S3_0_C0_C5_3
S3_0_C0_C5_6
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #18 from Paul Floyd --- commit 60fca88acc9311fbd910f852f0761110a21cd7e8 (HEAD -> master, origin/master, origin/HEAD) Author: Paul Floyd Date: Wed May 22 08:01:40 2024 +0200 arm64 regtest: add a configure check that the compiler accepts sha3. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 453044] gbserver_tests failures in aarch64
https://bugs.kde.org/show_bug.cgi?id=453044 --- Comment #5 from Paul Floyd --- glibc 2.28 I meant -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 453044] gbserver_tests failures in aarch64
https://bugs.kde.org/show_bug.cgi?id=453044 --- Comment #4 from Paul Floyd --- (In reply to Jesus Checa from comment #3) > (In reply to Paul Floyd from comment #2) > > Which version of gdb was this with? > > This was gdb 8.2 I just tried building gdb and couldn't reproduce. Quite likely this is due to the glibc version. I only have access to systems that are older or newer than 2.18. The patch looks safe, I'll do some tests and if nothing breaks I'll push it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 462958] ARMv8: Unrecognised instruction: _armv8_sha512_probe
https://bugs.kde.org/show_bug.cgi?id=462958 Paul Floyd changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Paul Floyd --- Can you confirm that this is fixed by the changes in 447989? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989
Paul Floyd changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED |---
Ever confirmed|0 |1
--- Comment #16 from Paul Floyd ---
I need to add a sha3 feature test. sha512_v82 fails to build on a Cavium
thunderx2t99.
diff --git a/configure.ac b/configure.ac
index 8792150..20ff73e 100755
--- a/configure.ac
+++ b/configure.ac
@@ -5618,6 +5618,23 @@ AC_MSG_RESULT([no])
AM_CONDITIONAL(HAVE_THRD_CREATE, test x$ac_cxx_have_thrd_create = xyes)
+# Check arm64 sha3
+safe_CFLAGS=$CFLAGS
+CFLAGS="${CFLAGS} -march=armv8.2-a+sha3"
+AC_MSG_CHECKING([for sha3])
+AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]], [[
+ return 0;
+]])],
+[
+ac_have_sha3=yes
+AC_MSG_RESULT([yes])
+], [
+ac_have_sha3=no
+AC_MSG_RESULT([no])
+])
+
+AM_CONDITIONAL(HAVE_SHA3, test x$ac_have_sha3 = xyes)
+CFLAGS=$safe_CFLAGS
#
# Ok. We're done checking.
diff --git a/none/tests/arm64/Makefile.am b/none/tests/arm64/Makefile.am
index 296000d..071cce0 100644
--- a/none/tests/arm64/Makefile.am
+++ b/none/tests/arm64/Makefile.am
@@ -45,7 +45,11 @@ if BUILD_ARMV81_TESTS
endif
if BUILD_ARMV82_TESTS
- check_PROGRAMS += fp_and_simd_v82 sha512_v82
+ check_PROGRAMS += fp_and_simd_v82
+endif
+
+if HAVE_SHA3
+ check_PROGRAMS += sha512_v82
endif
if HAVE_CXX17
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 290061] pie elf always loaded at 0x108000
https://bugs.kde.org/show_bug.cgi?id=290061 --- Comment #6 from Paul Floyd --- The patch no longer applies cleanly. Currently there is some special case code for mips64. I've tried to access a suitable machine to check if this is still relevant, but no success so far. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #15 from Paul Floyd --- I got some AWS credits from the FreeBSD dev that makes everything work on ec2, no problems with the patch. Thanks again. commit 5bf987891972478376e816fefea2d9abac3cb4fe (origin/master, origin/HEAD) Author: David Benjamin Date: Wed Jan 5 00:22:30 2022 -0500 Add support for Armv8.2 SHA-512 instructions Fixes https://bugs.kde.org/show_bug.cgi?id=447989 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487263] New: Cursor is hidden while hovering over maps in Kstars
https://bugs.kde.org/show_bug.cgi?id=487263 Bug ID: 487263 Summary: Cursor is hidden while hovering over maps in Kstars Classification: Applications Product: kstars Version: 3.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: phome...@bigpond.net.au Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The cursor / pointer is visible while hovering over the menues but disappears when placed over the mapping area. STEPS TO REPRODUCE 1. Hover over star map in Kstars 2. 3. OBSERVED RESULT Cursor is invisible EXPECTED RESULT Cursor remains visible. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Raspberry Pi Bookworm (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This is a build from today's source. Stellarsolver/INDI/Kstars and PHD2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486222] Unable to have Unity style panel layout in Plasma 6 (can't have maximum width panel on the top with another panel on the left)
https://bugs.kde.org/show_bug.cgi?id=486222 paul.magel@gmailcom changed: What|Removed |Added CC||paul.ma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #13 from Paul Floyd --- Thanks for the patches. I've applied, tested and pushed the first one. The second patch looks OK so far but I'd like to check it on FreeBSD before pushing the change. It might take me a little while to see if I can get my hands on a suitable machine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487183] Improper dragging and resizing behavior for windows that started in maximized state
https://bugs.kde.org/show_bug.cgi?id=487183 Paul Worrall changed: What|Removed |Added Resolution|--- |DUPLICATE CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 486603 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486603] Opening certain windows in maximized state and then de-maximizing them by dragging the title bar results in improper sizes
https://bugs.kde.org/show_bug.cgi?id=486603 Paul Worrall changed: What|Removed |Added CC||oleksandr.chekhovskyi@gmail ||.com --- Comment #11 from Paul Worrall --- *** Bug 487183 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 290061] pie elf always loaded at 0x108000
https://bugs.kde.org/show_bug.cgi?id=290061 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487111] Massif crash on Android API >= 30 due to tagged pointers
https://bugs.kde.org/show_bug.cgi?id=487111 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- It looks like malloc is getting redirected but not free, which would probably crash anyway even without MTE. Has Android changed the visibility of 'free' in any way? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Paul Floyd changed: What|Removed |Added CC||lefer...@gmail.com --- Comment #96 from Paul Floyd --- *** Bug 487124 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487124] Unhandled instruction bytes amd64 CentOS 7
https://bugs.kde.org/show_bug.cgi?id=487124 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED CC||pjfl...@wanadoo.fr Resolution|--- |DUPLICATE --- Comment #1 from Paul Floyd --- I believe that this is vpxord which is avx512. *** This bug has been marked as a duplicate of bug 383010 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 411203] valgrind should have a mean to pass environment variable to target program
https://bugs.kde.org/show_bug.cgi?id=411203 --- Comment #6 from Paul Floyd --- It would probably be easiest to do this in valgrind itself. It already does this to insert LD_PRELOADs for the core and tool vgpreaload libs. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #9 from Paul Floyd --- (In reply to David Benjamin from comment #8) > Regarding the generating the expected files by running the test, I assume > those just record what my patch does. I.e. if my patch were wrong, the wrong > things would get recorded in expectations. I've run my test against > BoringSSL's use of these instructions, so I'm fairly confident it's correct. > But it seems to me we can do better: just synthesize the expected output by > running the instructions directly, without involving valgrind at all. Yes. Generally for the error detecting tools the stderr.exp file checks that the errors are detected (and that there are no false positives). The 'none' tests ensure that the opcodes are handled and they usually 'printf' random values that get fed into the FP or crypto opcodes. Running the standalone exe to generate the stdout.exp files is probably the best. There are some rare cases when it needs to be done with Valgrind (usually when the exe using client requests to change code paths). > I don't suppose this exists? (If not, no big deal. Like I said, I've already > manually tested this against BoringSSL.) There are some perl scripts for testcase generation. For instance see none/tests/amd64/gen_insn_test.pl Otherwise I just use a lot of copy and paste. > Regarding where to put the tests, these are indeed Armv8.2 instructions, but > I noticed fp_and_simd_v82's prerequisite is actually the fphp (floating > point half-precision) extension. These instructions are from a separate > extension. My test device happens to have both but, in principle, they're > orthogonal. > > Should I still put them in fp_and_simd_v82 or make a new one? I'm guessing a > new one would be preferable, though this would get pretty large fast. Arm, > alas, has lots and lots of extensions. E.g. I noticed that the Armv8.0 > cryptography instructions are just in the plain fp_and_simd test, with no > prereq, but not all Armv8.0 chips have those instructions. (It's pretty rare > to omit them, but I think the Raspberry Pis don't?) > > If I make a new one, should I just copy all the various helper macros at the > top of that file, or try to extract them somewhere? Seems they're in a few > places already. I'm not really an ARM expert. It sounds like it would be best to create a new test and refactor the helpers into a single header. For the extensions and -march (and -mcpu -mthumb -marm) it's all a bit of a mess. For instance see https://bugs.kde.org/show_bug.cgi?id=454346. All I ran really say is that it worked for the original environment used for the arm64 port (qemu afaict) and it works on my Pi 5, the sourceware buildbot farm and the few other aarch64 machines that I have access to. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352021] Signals are ignored in OS X 10.10
https://bugs.kde.org/show_bug.cgi?id=352021 --- Comment #8 from Paul Floyd --- Still hanging. Need to look at is_signal_from_kernel to see if anything has changed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #7 from Paul Floyd --- (In reply to David Benjamin from comment #6) > This was quite some time ago, so I'll have to page this back in and remind > myself how I tested this. :-) > > > This will also need a change in arm64g_dirtyhelper_MRS_ID_AA64ISAR0_EL1 > > I don't believe that code was there when I first uploaded the patch, but > yeah, I can update that. Yes, it only recently got added. > Do you have any pointers? I think that in this case I would just add sha512 tests to none/tests/fp_and_simd (or fp_and_simd_v82 - I'm not sure what the minimum version is for sha512). Otherwise I just added a section to README_DEVELOPERS on writing regression tests. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487055] memcheck/tests/x86-linux/scalar fails running in Docker
https://bugs.kde.org/show_bug.cgi?id=487055 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487055] memcheck/tests/x86-linux/scalar fails running in Docker
https://bugs.kde.org/show_bug.cgi?id=487055 Paul Floyd changed: What|Removed |Added Summary|memcheck/tests/x86-linux/sc |memcheck/tests/x86-linux/sc |alar fails runing in Docker |alar fails running in ||Docker -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487055] memcheck/tests/x86-linux/scalar fails runing in Docker
https://bugs.kde.org/show_bug.cgi?id=487055 --- Comment #2 from Paul Floyd --- On second thoughts, just SUCC_OR_FAIL would be easier, but test a bit less. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487055] memcheck/tests/x86-linux/scalar fails runing in Docker
https://bugs.kde.org/show_bug.cgi?id=487055
--- Comment #1 from Paul Floyd ---
Out by one, it was 'nice' not 'ftime'. This patch works form me
--- a/memcheck/tests/x86-linux/scalar.c
+++ b/memcheck/tests/x86-linux/scalar.c
@@ -32,6 +32,11 @@ int main(void)
long x0 = px[0];
long res;
+ int in_docker = 0;
+ if (access("/.dockerenv", F_OK) == 0) {
+ in_docker = 1;
+ }
+
// All __NR_xxx numbers are taken from x86
// __NR_restart_syscall 0 // XXX: not yet handled, perhaps should be...
@@ -190,7 +195,12 @@ int main(void)
// __NR_nice 34
GO(__NR_nice, "1s 0m");
- SY(__NR_nice, x0); SUCC;
+ SY(__NR_nice, x0);
+ if (in_docker) {
+ FAIL;
+ } else {
+ SUCC;
+ }
// __NR_ftime 35
GO(__NR_ftime, "ni");
(also need to update the expected).
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 487055] New: memcheck/tests/x86-linux/scalar fails runing in Docker
https://bugs.kde.org/show_bug.cgi?id=487055 Bug ID: 487055 Summary: memcheck/tests/x86-linux/scalar fails runing in Docker Classification: Developer tools Product: valgrind Version: 3.24 GIT Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: pjfl...@wanadoo.fr Target Milestone: --- The end of the unfiltered log is - 34: __NR_nice 1s 0m - ==263012== Syscall param nice(inc) contains uninitialised byte(s) ==263012==at 0x415AD57: syscall (in /usr/lib/libc-2.17.so) ==263012==by 0x8049EC2: main (scalar.c:193) ==263012== scalar: scalar.c:193: main: Assertion `-1 != res' failed. That means that ftime is not failing. Probably a difference in the Docker virtualization. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352021] Signals are ignored in OS X 10.10
https://bugs.kde.org/show_bug.cgi?id=352021 --- Comment #7 from Paul Floyd --- Can't easily try this on 10.10. I'll have a go with a 10.13 VM. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352021] Signals are ignored in OS X 10.10
https://bugs.kde.org/show_bug.cgi?id=352021 Paul Floyd changed: What|Removed |Added Assignee|rhysk...@gmail.com |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372779] valgrind will hang on OSX 10.11
https://bugs.kde.org/show_bug.cgi?id=372779 Paul Floyd changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Paul Floyd --- 10.11 is long in the tooth now. Can anyone provide a reproducer? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 462958] ARMv8: Unrecognised instruction: _armv8_sha512_probe
https://bugs.kde.org/show_bug.cgi?id=462958 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989
--- Comment #5 from Paul Floyd ---
This will also need a change in arm64g_dirtyhelper_MRS_ID_AA64ISAR0_EL1
This bit will need to be removed
/* Degredate SHA2 from b0010 to b0001*/
if ( (w >> 12) & 0x2 ) {
w ^= (0x2 << 12);
w |= (0x1 << 12);
}
And at least one testcase would also be good!
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #4 from Paul Floyd --- (In reply to Paul Floyd from comment #3) > (In reply to David Benjamin from comment #2) > > Anything needed before this patch is submittable? > > Someone actively working on the ARM version of Valgrind? ^^^ well now that's me, time to look atthis again. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 454346] [PATCH] ARM fixes from the Yocto project
https://bugs.kde.org/show_bug.cgi?id=454346 --- Comment #11 from Paul Floyd --- (In reply to Khem Raj from comment #10) > Hmm, I think we need to use -march=armv7ve instead of -mcpu=cortex-a8, I did > realize that all distros > will not tune the compiler like yocto does. The build and tests need to run with just autogen.sh, configure (without compiler options), make, make check and make regtest. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426798] 404 link in Valgrind website for valkyrie
https://bugs.kde.org/show_bug.cgi?id=426798 Paul Floyd changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Paul Floyd --- commit 25e550574acc1e5c9f81956081797dc511950603 (HEAD -> main, origin/main, origin/HEAD) Author: Paul Floyd Date: Tue May 14 20:02:36 2024 +0200 Bug 426798 - 404 link in Valgrind website for valkyrie -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426798] 404 link in Valgrind website for valkyrie
https://bugs.kde.org/show_bug.cgi?id=426798 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 454346] [PATCH] ARM fixes from the Yocto project
https://bugs.kde.org/show_bug.cgi?id=454346 --- Comment #9 from Paul Floyd --- On my RPi 5 with Raspberry Pi OS Linux raspberrypi 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux Build fails with m_dispatch/dispatch-arm-linux.S:102: Error: selected processor does not support `movw r1,#47' in ARM mode m_dispatch/dispatch-arm-linux.S:103: Error: selected processor does not support `movw r2,#0' in ARM mode m_dispatch/dispatch-arm-linux.S:155: Error: selected processor does not support `movw r4,#:lower16:vgPlain_stats__n_xIndirs_32' in ARM mode m_dispatch/dispatch-arm-linux.S:156: Error: selected processor does not support `movt r4,#:upper16:vgPlain_stats__n_xIndirs_32' in ARM mode m_dispatch/dispatch-arm-linux.S:173: Error: selected processor does not support `ubfx r6,r6,#0,#13' in ARM mode m_dispatch/dispatch-arm-linux.S:176: Error: selected processor does not support `movw r4,#:lower16:vgPlain_tt_fast' in ARM mode m_dispatch/dispatch-arm-linux.S:177: Error: selected processor does not support `movt r4,#:upper16:vgPlain_tt_fast' in ARM mode m_dispatch/dispatch-arm-linux.S:204: Error: selected processor does not support `movw r4,#:lower16:vgPlain_stats__n_xIndir_hits1_32' in ARM mode m_dispatch/dispatch-arm-linux.S:205: Error: selected processor does not support `movt r4,#:upper16:vgPlain_stats__n_xIndir_hits1_32' in ARM mode m_dispatch/dispatch-arm-linux.S:226: Error: selected processor does not support `movw r4,#:lower16:vgPlain_stats__n_xIndir_hits2_32' in ARM mode m_dispatch/dispatch-arm-linux.S:227: Error: selected processor does not support `movt r4,#:upper16:vgPlain_stats__n_xIndir_hits2_32' in ARM mode m_dispatch/dispatch-arm-linux.S:248: Error: selected processor does not support `movw r4,#:lower16:vgPlain_stats__n_xIndir_hits3_32' in ARM mode m_dispatch/dispatch-arm-linux.S:249: Error: selected processor does not support `movt r4,#:upper16:vgPlain_stats__n_xIndir_hits3_32' in ARM mode m_dispatch/dispatch-arm-linux.S:258: Error: selected processor does not support `movw r4,#:lower16:vgPlain_stats__n_xIndir_misses_32' in ARM mode m_dispatch/dispatch-arm-linux.S:259: Error: selected processor does not support `movt r4,#:upper16:vgPlain_stats__n_xIndir_misses_32' in ARM mode and also gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../include -I../VEX/pub -I../VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 -DVGPV_arm_linux_vanilla=1-O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-signedness -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wenum-conversion -Wimplicit-fallthrough=2 -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -marm -O2 -MT memcheck_arm_linux-mc_main.o -MD -MP -MF .deps/memcheck_arm_linux-mc_main.Tpo -c -o memcheck_arm_linux-mc_main.o `test -f 'mc_main.c' || echo './'`mc_main.c /tmp/ccY1NRlM.s: Assembler messages: /tmp/ccY1NRlM.s:27: Error: selected processor does not support `movw r3,#:lower16:primary_map' in ARM mode /tmp/ccY1NRlM.s:29: Error: selected processor does not support `movt r3,#:upper16:primary_map' in ARM mode /tmp/ccY1NRlM.s:68: Error: selected processor does not support `movw r3,#:lower16:primary_map' in ARM mode /tmp/ccY1NRlM.s:70: Error: selected processor does not support `movt r3,#:upper16:primary_map' in ARM mode gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../include -I../VEX/pub -I../VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 -DVGPV_arm_linux_vanilla=1-O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-signedness -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wenum-conversion -Wimplicit-fallthrough=2 -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -marm -O2 -MT memcheck_arm_linux-mc_main_asm.o -MD -MP -MF .deps/memcheck_arm_linux-mc_main_asm.Tpo -c -o memcheck_arm_linux-mc_main_asm.o `test -f 'mc_main_asm.c' || echo './'`mc_main_asm.c /tmp/cclkrIER.s: Assembler messages: /tmp/cclkrIER.s:25: Error: selected processor does not support `movw r3,#:lower16:primary_map' in ARM mode /tmp/cclkrIER.s:28: Error: selected processor does not support `movt r3,#:upper16:primary_map' in ARM mode /tmp/cclkrIER.s:31: Error: selected processor does not support `movw r3,#0x' in ARM mode /tmp/cclkrIER.s:40: Error: selected processor does not support `movw r3,#0x' in ARM mode /tmp/cclkrIER.s:61: Error: selected processor does not support `movw r3,#:lower16:primary_map' in ARM mode /tmp/cclkrIER.s:64: Error: selected processor does not support `movt r3,#:upper16:primary_map' in ARM mode -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353471] memcheck/tests/x86/xor-undef-x86 fails on OS X 10.11
https://bugs.kde.org/show_bug.cgi?id=353471 Paul Floyd changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Paul Floyd --- With the patch from 282910 this testcase now passes on 10.13. Can't easily test this on 10.11. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 348909] Support OS X 10.11 (El Capitan)
https://bugs.kde.org/show_bug.cgi?id=348909 Bug 348909 depends on bug 353471, which changed state. Bug 353471 Summary: memcheck/tests/x86/xor-undef-x86 fails on OS X 10.11 https://bugs.kde.org/show_bug.cgi?id=353471 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 276780] An instruction in fftw (Fast Fourier Transform) is unhandled by valgrind: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22
https://bugs.kde.org/show_bug.cgi?id=276780 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Paul Floyd --- commit 92b6fa13d4ecf075c434d0316d493383edf7aa6d (HEAD -> master, origin/master, origin/HEAD) Author: Tom Hughes Date: Mon May 13 20:40:19 2024 +0200 Bug 276780 - An instruction in fftw (Fast Fourier Transform) is unhandled by valgrind: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 276780] An instruction in fftw (Fast Fourier Transform) is unhandled by valgrind: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22
https://bugs.kde.org/show_bug.cgi?id=276780 Paul Floyd changed: What|Removed |Added CC||t...@compton.nu -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 276780] An instruction in fftw (Fast Fourier Transform) is unhandled by valgrind: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22
https://bugs.kde.org/show_bug.cgi?id=276780 --- Comment #4 from Paul Floyd --- Created attachment 169455 --> https://bugs.kde.org/attachment.cgi?id=169455=edit Added testcase NEWS and .gitignore -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 276780] An instruction in fftw (Fast Fourier Transform) is unhandled by valgrind: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22
https://bugs.kde.org/show_bug.cgi?id=276780 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 --- Comment #33 from Paul Floyd --- (In reply to Matthias Brugger from comment #32) > It's good to see that this got fixed. That said it seems that the community > process in valgrind is somewhat broken. I sent a fix, it went silent for > nearly 6 years. I don't have a solution to that. We need more contributors. > You took up the work, did a small change and pushed that > right away, no review or possibility to fix it myself. Again I don't have a solution for that. I don't feel that we have enough contributors to be able to review all changes - if we had more than I would be in favour of having everything reviewed. I did hurry these changes a bit as I had a few days holiday and I wanted to get it finished. I did send a mail in private to Peter Maydell asking if he had any comments on these changes. Please let us know if you seen anything that looks wrong. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486916] Plasma doesn't honor the "effects" of Inkscape (.svg)
https://bugs.kde.org/show_bug.cgi?id=486916 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #3 from Paul Worrall --- Could you attach the actual .svg file that has the problem? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486914] musl: all helgrind testcases fail
https://bugs.kde.org/show_bug.cgi?id=486914 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486914] New: musl: all helgrind testcases fail
https://bugs.kde.org/show_bug.cgi?id=486914 Bug ID: 486914 Summary: musl: all helgrind testcases fail Classification: Developer tools Product: valgrind Version: 3.24 GIT Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: helgrind Assignee: jsew...@acm.org Reporter: pjfl...@wanadoo.fr Target Milestone: --- There are at least 3 problems. 1. The redirects for Linux glibc often have @*, musl doesn't. Need to add musl-specific redirects. 2. As a consequence of 2. the expecteds all contain @*. For FreeBSD I added an awk filter to add the required @*, should be possible to reuse the filter. 3. pthread_rwlock functions are implemented in using other public pthread_rwlock functions, e.g. https://elixir.bootlin.com/musl/latest/source/src/thread/pthread_rwlock_rdlock.c which causes spurious recursive lock warnings. Only the innermost function should be redirected (not great for error messages). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 450788] unhandled instruction 0xD50B7A22 [aarch64]
https://bugs.kde.org/show_bug.cgi?id=450788 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Paul Floyd --- 0xD50B7A22 is dc cvac, this should now be handled. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 450788] unhandled instruction 0xD50B7A22 [aarch64]
https://bugs.kde.org/show_bug.cgi?id=450788 Paul Floyd changed: What|Removed |Added Summary|valgrind: Unrecognised |unhandled instruction |instruction at address |0xD50B7A22 [aarch64] |0x8f24da0 [aarch64] | Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 453044] gbserver_tests failures in aarch64
https://bugs.kde.org/show_bug.cgi?id=453044 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr Assignee|jsew...@acm.org |pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd --- Which version of gdb was this with? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 430117] Implement guest Arm64/AArch64 feature detection support for v8 instructions
https://bugs.kde.org/show_bug.cgi?id=430117 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- I think that this was mostly resolved with 9ecbb9037b596babf69745f9e212c80b2cef4174 [Bug 392146 - aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1)] Specifically, MRS ID_AA64ISAR0_EL1 end similar registers are now handled, with filtering in the dirty helper to filter out unsupported features. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377966] arm64 unhandled instruction dc zva
https://bugs.kde.org/show_bug.cgi?id=377966 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #11 from Paul Floyd --- commit 8b6c36ecf14530d7f50f65697c2a039e3d410092 (HEAD -> master, origin/master, origin/HEAD) Author: Paul Floyd Date: Sat May 11 18:10:03 2024 +0200 Bug 377966 - arm64 unhandled instruction dc zva With contributions from Louis Brunner https://github.com/LouisBrunner/valgrind-macos -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 486875] Microsoft keyboard does not work in plasma
https://bugs.kde.org/show_bug.cgi?id=486875 Paul Worrall changed: What|Removed |Added Resolution|--- |NOT A BUG CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377966] arm64 unhandled instruction dc zva
https://bugs.kde.org/show_bug.cgi?id=377966 --- Comment #10 from Paul Floyd --- In addition to the opcode this will also require that MRS DCZID_EL0 reads the DZP flag correctly - currently it is hard coded to 1 (which prohibits fc zva). https://developer.arm.com/documentation/ddi0595/2021-06/AArch64-Registers/DCZID-EL0--Data-Cache-Zero-ID-register?lang=en -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 412377] SIGILL on cache flushes on arm64
https://bugs.kde.org/show_bug.cgi?id=412377 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from Paul Floyd --- commit d39ba3bade49483d7c1067405a881b214e895cf9 (HEAD -> master, origin/master, origin/HEAD) Author: Paul Floyd Date: Sat May 11 15:21:47 2024 +0200 Bug 412377 - SIGILL on cache flushes on arm64 Patch contributed by Adam Borowski -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440095] No support for "dc cvac" and "dc cvap" on Arm64
https://bugs.kde.org/show_bug.cgi?id=440095 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED CC||pjfl...@wanadoo.fr Status|REPORTED|RESOLVED --- Comment #9 from Paul Floyd --- commit 40505e5056a7e434e291526d6662943e31274fc1 (HEAD -> master, origin/master, origin/HEAD) Author: Kevin Zhao Date: Thu Jul 22 16:00:21 2021 +0800 arm64 front end: add support for 'dc cvac', 'dc cvap', handling it the same as 'dc cvau'. patch modified to process DBP component of ID_AA64ISAR1_EL1 Signed-off-by: Kevin Zhao -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #31 from Paul Floyd --- I might add a test or two later. Not easy to write something that is really hardware independent. commit 9ecbb9037b596babf69745f9e212c80b2cef4174 (HEAD -> master, origin/master, origin/HEAD) Author: Paul Floyd Date: Sat May 11 13:53:42 2024 +0200 Bug 392146 - aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 --- Comment #30 from Paul Floyd --- Going through the patch register by register. MIDR_EL1 I think that this is OK and can be applied as-is. I might try to write a test that generates the expected on the fly. MPIDR_EL1 FreeBSD sets the affinity masks and MT. I don't think that is of any concern in Valgrind so I'll ignore it for now. REVDIR_EL1 same as standalone on both platforms ID_AA64PFR0_EL1 looks OK. Also turns off all the exception level settings but from what I see that only affects kernel code and userland is all EL0 ID_AA64PFR1_EL1 looks OK, this is turning off a flag that says the CPU can mark regions as speculation safe, meaningless under Valgrind. ID_AA64ZFR0_EL1 looks OK, FreeBSD sets BRP and WRP - hardware debug registers. Might affect gdb or lldb under Valgrind, or are they only for kernel debuggers? ID_AA64DFR1_EL1 looks OK manual says this returns 64bits RES0 ID_AA64AFR0_EL1 looks OK manual says this is RES0 / implementation defined ID_AA64AFR1_EL1 looks OK manual says this returns 64bits RES0 ID_AA64ISAR0_EL1 ISA feature register. Fairly important! In the patch + /* Clear all but AES, SHA1 and SHA2 parts*/ + w &= ~0x; That looks wrong to me. AES and SHA are in the lowest 16 bits, I think that negation shouldn't be there. We need to set DP bits 47-44 (if available on the underlying hardware) since f42b9a434e12bc14ec821183a69b86e91da0577c added those instructions. We need to set RDM bits 31-28 since a8c274d0682b7265af7a5a9c71251d48169c9dc9 We need to set Atomic bits 23-20 since f1cf734554320e92f0dfc80125dfc2a7e5356ff2 Finally we need to set CRC32 since 6c99d37dd036d562b6a56cce576d125d0d239a3a The lowest 16 bits are already covered above. ID_AA64ISAR1_EL1 more ISA features OK for the moment, will need to be updated when https://bugs.kde.org/show_bug.cgi?id=440095 gets applied ID_AA64MMFR0_EL1 ID_AA64MMFR1_EL1 ID_AA64MMFR2_EL1 First two just pass values via dirty helpers. Last one uses constant zero. Looks OK. So, in summary, I'll look at updating ID_AA64ISAR0_EL1, think about writing some tests. And look at the other registers later. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486812] Valgrind reports read errors reading a memory area that has been used as `sigaltstack` memory
https://bugs.kde.org/show_bug.cgi?id=486812 Paul Floyd changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Paul Floyd --- I see that you've disabled the test without even understanding the problem. That's the kind of quality that I expect from GTK. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 --- Comment #29 from Paul Floyd --- Created attachment 169365 --> https://bugs.kde.org/attachment.cgi?id=169365=edit arm64id output on FreeBSD under Valgrind with patch Not looking too good. Several bits of the patch just write constants whilst FreeBSD does seem to implement the ARM spec. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 Paul Floyd changed: What|Removed |Added Summary|aarch64: unhandled |aarch64: unhandled |instruction 0xD5380001 (MRS |instruction 0xD5380001 (MRS |rT, mdir_el1) |rT, midr_el1) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486844] New: Trash settings: size limit initially greyed-out
https://bugs.kde.org/show_bug.cgi?id=486844 Bug ID: 486844 Summary: Trash settings: size limit initially greyed-out Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Trash Assignee: plasma-b...@kde.org Reporter: p.r.worr...@gmail.com Target Milestone: 1.0 When first launching the settings dialog for trash/waste-bin, "Size" is checked, but the box for setting the size is disabled. You have to toggle "Size" to activate it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339405] [PATCH] Adds ability to invoke a script in order to determine a log-file name for a child being forked
https://bugs.kde.org/show_bug.cgi?id=339405 Paul Floyd changed: What|Removed |Added Summary|Adds ability to invoke a|[PATCH] Adds ability to |script in order to |invoke a script in order to |determine a log-file name |determine a log-file name |for a child being forked|for a child being forked -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486812] Valgrind reports read errors reading a memory area that has been used as `sigaltstack` memory
https://bugs.kde.org/show_bug.cgi?id=486812 --- Comment #1 from Paul Floyd --- I have a workaround - use KDE :-) ==451300==by 0x10BB30: memset (string_fortified.h:59) memcheck should be redirecting memset, which it expects to be in libc. Is that a fortified version that is inline in a header? Can you build a non-fortified version for testing with Valgrind. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339405] Adds ability to invoke a script in order to determine a log-file name for a child being forked
https://bugs.kde.org/show_bug.cgi?id=339405 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127 --- Comment #19 from Paul Floyd --- (In reply to Mark Wielaard from comment #18) > I must admit I don't fully understand what we are trying to do. As far as I > understand it, the idea is that we sanity check what the aspacemgr records > against what /proc/self/maps shows? But that includes some device specific > inode values which we don't have/know? Can't we just make cmp_devino = False > the default? aka never check those? Or are we loosing some valuable sanity > checks/info that way? I think the goal is to check as many things as possible. Is it valuable? Hard to imagine reading the wrong exe or library that is mmap'd but if ever that did happen it would be fairly catastrophic. The problem with btrfs is that /proc/self/maps uses the device id for the supernode whilst statx returns the device id for the btrfs subvolume. The two are different so the sanity check fails. This check is turned off for Darwin. I'm just testing turning it back on for FreeBSD - it seems to work with a couple of tweaks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486538] Running a program linked with mold causes the debuginfo reader to stop working
https://bugs.kde.org/show_bug.cgi?id=486538 Paul Floyd changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #7 from Paul Floyd --- dwarfdump -ka also gives me *** DWARF CHECK: .debug_ranges: Address outside a valid .text range *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486538] Running a program linked with mold causes the debuginfo reader to stop working
https://bugs.kde.org/show_bug.cgi?id=486538 --- Comment #6 from Paul Floyd --- After debugging this again I've come to the conclusion that the code is a mess but probably correct. I've reproduced a DIFFERENT error from the GH report [paulf@archlinux bug]$ ~/valgrind/vg-in-place ./wrong_exe ==23366== Memcheck, a memory error detector ==23366== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==23366== Using Valgrind-3.24.0.GIT and LibVEX; rerun with -h for copyright info ==23366== Command: ./wrong_exe ==23366== ==23366== Valgrind: debuginfo reader: ensure_valid failed: ==23366== Valgrind: during call to ML_(img_strdup) ==23366== Valgrind: request for range [36949181, +1) exceeds ==23366== Valgrind: valid image size of 36802224 for image: ==23366== Valgrind: "/home/paulf/bug/wrong_exe" -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486744] /bin/sh: bad interpreter: input/output error - while executing a file on a CIFS share
https://bugs.kde.org/show_bug.cgi?id=486744 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Paul Worrall --- This is not an issue with KDE software, I suggest you search for the solution elsewhere, maybe https://unix.stackexchange.com/questions/34822/is-it-possible-to-enable-execution-of-files-from-a-cifs-mount-in-bash -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486538] Running a program linked with mold causes the debuginfo reader to stop working
https://bugs.kde.org/show_bug.cgi?id=486538 --- Comment #5 from Paul Floyd --- I can't see a problem in your logs. But looking at the code things do look wrong. For example, when loading /usr/home/paulf/scratch/valgrind/memcheck/vgpreload_memcheck-amd64-freebsd.so The PT_LOADs are LOAD off0x vaddr 0x paddr 0x align 2**12 filesz 0x5fc4 memsz 0x5fc4 flags r-- LOAD off0x5fd0 vaddr 0x6fd0 paddr 0x6fd0 align 2**12 filesz 0xcfd0 memsz 0xcfd0 flags r-x LOAD off0x00012fa0 vaddr 0x00014fa0 paddr 0x00014fa0 align 2**12 filesz 0x0190 memsz 0x0190 flags rw- LOAD off0x00013130 vaddr 0x00016130 paddr 0x00016130 align 2**12 filesz 0x0058 memsz 0x00e8 flags rw- And some debug traces with // comments (these values come from the client mmap) DEBUG: vgPlain_di_notify_mmap start 0x4846000 end 0x484BFFF size 6000 offset 0 // RO DEBUG: vgPlain_di_notify_mmap start 0x484C000 end 0x4859FFF size e000 offset 5000 // RX DEBUG: vgPlain_di_notify_mmap start 0x485A000 end 0x485BFFF size 2000 offset 12000 // RW1 DEBUG: vgPlain_di_notify_mmap start 0x485C000 end 0x485CFFF size 1000 offset 13000 // RW2 My reading of that is that the mmap offset is the ELF offset page rounded down. The mmap size is harder to follow. The first RO one is page rounded up. The second RX and third RW1 look like they are page rounded up plus one page (because of the overlap?). The last RW2 looks just page rounded up. ML_(read_elf_object) uses Bool offset_checks = a_phdr.p_offset >= map->foff && a_phdr.p_offset < map->foff + map->size && a_phdr.p_offset + a_phdr.p_filesz <= map->foff + map->size; That's mixing mmap and ELF values. RW1 gets added twice because 0x13130 is within both offset 0x12000 size 0x2000 and offset 0x13000 size 0x1000. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486569] linux inotify_init syscall wrapper missing POST entry in syscall_table
https://bugs.kde.org/show_bug.cgi?id=486569 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Paul Floyd --- commit b38115cc6087f30f872c533f93c7c31a6d73eb24 Author: Paul Floyd Date: Sat May 4 15:03:11 2024 +0200 Bug 486569 - linux inotify_init syscall wrapper missing POST entry in syscall_table -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 486705] Should give KDE frameworks plamsa and qt versions in help about
https://bugs.kde.org/show_bug.cgi?id=486705 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #1 from Paul Worrall --- That information is in Info Centre (Application Launcher=>System=>Info Centre) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127 --- Comment #17 from Paul Floyd --- And with the patch I get a clean slate == 880 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127 --- Comment #16 from Paul Floyd --- The patch I just added seems to work OK. There is a plan B. In the patch I've also updated the statx structure which (since kernel 5.8) has an stx_mnt_id which we could try to use. I don't know how many people are still using old kernels with btrfs. Not too many I imagine. The 5.8 kernel dates back to Fedora 33. And no guarantee that stx_mnt_id would work. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127 --- Comment #15 from Paul Floyd --- Created attachment 169247 --> https://bugs.kde.org/attachment.cgi?id=169247=edit patch, amd64 only Initial version of a fix. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127
--- Comment #14 from Paul Floyd ---
I think that the answer is to add something like
VG_(do_syscall3)(__NR_statfs, filename, );
if (statfs.f_type == BTRFS_SUPER_MAGIC) {
cmp_devino = False;
}
inside the existing VGO_linux block.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #13 from Paul Floyd --- *** Bug 486662 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486662] Running with --sanity-level=3 or higher fails on Linux using btrfs
https://bugs.kde.org/show_bug.cgi?id=486662 Paul Floyd changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Paul Floyd --- *** This bug has been marked as a duplicate of bug 317127 *** -- You are receiving this mail because: You are watching all bug changes.
