https://bugs.kde.org/show_bug.cgi?id=360571
Julian Seward changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=360571
--- Comment #11 from Julian Seward ---
Committed on trunk, r16073.
--
You are receiving this mail because:
You are watching all bug changes.
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, [r0, #0]"
https://bugs.kde.org/show_bug.cgi?id=360571
--- Comment #7 from Julian Seward ---
Created attachment 101476
--> https://bugs.kde.org/attachment.cgi?id=101476=edit
Proposed fix (lacks documentation, but seems to work)
For example, to keep the test program (next attachment)
https://bugs.kde.org/show_bug.cgi?id=360571
--- Comment #9 from Julian Seward ---
Anton, can you perhaps try this on aarch64 ? Would this work for you?
(Apologies .. there's one line in the test program you'll have to change.)
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=360571
--- Comment #8 from Julian Seward ---
Created attachment 101477
--> https://bugs.kde.org/attachment.cgi?id=101477=edit
A simple test program.
--
You are receiving this mail because:
You are watching all bug changes.
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.
https://bugs.kde.org/show_bug.cgi?id=360571
--- Comment #5 from Julian Seward ---
(In reply to Anton Kirilov from comment #4)
> Just a quick idea - do you think it is worth it supporting more than one
> range (e.g. for running code generated by a compiler that misbehaves in the
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
https://bugs.kde.org/show_bug.cgi?id=360571
--- Comment #3 from Julian Seward ---
(In reply to Anton Kirilov from comment #0)
> Currently, the workaround that I have been using is manually patching the
> Valgrind source code (in particular, the VG_GCC296_BUG_STACK_SLOP constant
https://bugs.kde.org/show_bug.cgi?id=360571
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--
You are
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.
https://bugs.kde.org/show_bug.cgi?id=360571
--- Comment #1 from Julian Seward ---
(In reply to Anton Kirilov from comment #0)
> The assembly language code that is emitted by ART at the beginning of each
> method, and that causes the warning, looks like this:
>
> sub r12, sp,
https://bugs.kde.org/show_bug.cgi?id=360571
Anton Kirilov changed:
What|Removed |Added
CC|
14 matches
Mail list logo