[valgrind] [Bug 386861] ARM64: Pre-indexed store to the stack reported as invalid write

https://bugs.kde.org/show_bug.cgi?id=386861 --- Comment #1 from Anton Kirilov --- Comment on attachment 108840 --> https://bugs.kde.org/attachment.cgi?id=108840 Test program >#include > >int main(void) >{ > uint64_t x = 1; > > __asm__ __volatile__ ( >#if 1 >

[valgrind] [Bug 386861] ARM64: Pre-indexed store to the stack reported as invalid write

https://bugs.kde.org/show_bug.cgi?id=386861 Anton Kirilov changed: What|Removed |Added CC||jacob.bramley+...@arm.com -- You are

[valgrind] [Bug 386861] New: ARM64: Pre-indexed store to the stack reported as invalid write

https://bugs.kde.org/show_bug.cgi?id=386861 Bug ID: 386861 Summary: ARM64: Pre-indexed store to the stack reported as invalid write Product: valgrind Version: 3.13.0 Platform: Android OS: unspecified

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

https://bugs.kde.org/show_bug.cgi?id=360571 --- Comment #10 from Anton Kirilov --- I tried the fix both on Aarch32 and Aarch64, and it worked. I just modified lines 35-36 of the test program to either: __asm__ __volatile__("sub r0, sp, #8192\n\tldr %0, [r

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

https://bugs.kde.org/show_bug.cgi?id=360571 --- Comment #6 from Anton Kirilov --- Just a theoretical question. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

https://bugs.kde.org/show_bug.cgi?id=360571 --- Comment #4 from Anton Kirilov --- (In reply to Julian Seward from comment #3) > An alternative is to introduce a new flag, something like this (eg) > > --ignore-accesses-below-sp-range=- > > so that just the specified range

[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 #2 from Anton Kirilov --- Yes, I can. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

https://bugs.kde.org/show_bug.cgi?id=360571 --- Comment #2 from Anton Kirilov --- Yes, that is correct. ART also sets up a signal handler for SIGSEGV. -- 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 Anton Kirilov changed: What|Removed |Added CC||jacob.bramley+...@arm.com -- You are

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

https://bugs.kde.org/show_bug.cgi?id=360574 Bug ID: 360574 Summary: Wrong parameter type for an ashmem ioctl() call on Android and ARM64 Product: valgrind Version: 3.11.0 Platform: Android OS: unspecified

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

https://bugs.kde.org/show_bug.cgi?id=360571 Anton Kirilov changed: What|Removed |Added CC||jacob.bramley+...@arm.com -- You are

[valgrind] [Bug 360571] New: Error about the Android Runtime reading below the stack pointer on ARM

https://bugs.kde.org/show_bug.cgi?id=360571 Bug ID: 360571 Summary: Error about the Android Runtime reading below the stack pointer on ARM Product: valgrind Version: 3.11.0 Platform: Android OS: unspecified