To make progress in the meantime, replace those 32 bits by the two instructions
mov r0,#0
mov r1,#0
which clear general registers r0 and r1. This is a guess that zeroes
mean "this CPU has no such hardware assist". The libcrypto software
will choose slower but equivalent code, instead o
On 6/29/2018 2:47 PM, Alan Corey wrote:
On 6/29/18, Edward Diener wrote:
On 6/28/2018 9:01 PM, Alan Corey wrote:
I'm no expert, but especially if it's arm64 try fetching the absolute
latest from https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=summary
That's about the error I got runnin
On 6/29/18, Edward Diener wrote:
> On 6/28/2018 9:01 PM, Alan Corey wrote:
>> I'm no expert, but especially if it's arm64 try fetching the absolute
>> latest from https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=summary
>>
>> That's about the error I got running versions before 3.13 on my Pi
On 6/29/2018 11:52 AM, John Reiser wrote:
https://bugs.kde.org/show_bug.cgi?id=396001
unhandled instruction: 0xEC51 0x0F1E; ARMv7 libcrypto 'mrrc'
Thanks. Looks like the bug needs to be fixed before I can use valgrind
successfully with libcrypto being loaded on my arm system.
---
On 6/28/2018 9:01 PM, Alan Corey wrote:
I'm no expert, but especially if it's arm64 try fetching the absolute
latest from https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=summary
That's about the error I got running versions before 3.13 on my Pi and
there was something similar even with 3.
On 6/29/2018 12:55 AM, John Reiser wrote:
On 06/28/2018, Edward Diener wrote:
I am attempting to use Valgrind with an application on an embedded arm
system.
==621== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright
info
==621== Command: ./myprogram
==621==
disInstr(thumb): unhand
https://bugs.kde.org/show_bug.cgi?id=396001
unhandled instruction: 0xEC51 0x0F1E; ARMv7 libcrypto 'mrrc'
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm
> On 18 Jun 2018, at 15:39, Ivo Raisr wrote:
>
> Dear Valgrind'ers,
>
> I have been maintaining the Valgrind Solaris (and partly also illumos)
> port for nearly three years,
> ensuring it builds and runs on the latest Solaris 11.1, 11.2, 11.3
> (and 11.4 until April 2018).
>
>
> I am still a
Hi Philippe - yes, I think you're right. I've reported a possible race
condition on RedHat's pthread_exit
(https://bugzilla.redhat.com/show_bug.cgi?id=1596537).
Thanks.
--
Check out the vibrant tech community on one of
