[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

https://bugs.kde.org/show_bug.cgi?id=360574 Julian Seward changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

https://bugs.kde.org/show_bug.cgi?id=360574 --- Comment #5 from Julian Seward --- Fixed, valgrind r15923. Thanks for the test. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

https://bugs.kde.org/show_bug.cgi?id=360574 --- Comment #4 from Anton Kirilov --- I have tested the patch, and it makes the error message disappear. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

https://bugs.kde.org/show_bug.cgi?id=360574 --- Comment #3 from Julian Seward --- The problem is that the wrappers for android-specific ioctls on 64-bit ARM are not enabled, so it handles them using the generic ioctl logic, which in this case isn't appropriate. Can you try this

[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

https://bugs.kde.org/show_bug.cgi?id=360574 --- Comment #2 from Anton Kirilov --- Yes, I can. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

https://bugs.kde.org/show_bug.cgi?id=360574 --- Comment #1 from Julian Seward --- Anton: I don't have an easily available arm64-android device to test on. But I think this is an easy fix. If I get you a patch, can you test it for me? -- You are receiving this mail because:

[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

https://bugs.kde.org/show_bug.cgi?id=360574 Anton Kirilov changed: What|Removed |Added CC|