Re: [Valgrind-users] Valgrind on arm system startup message

2018-06-29 Thread Edward Diener
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

Re: [Valgrind-users] Valgrind on arm system startup message

2018-06-29 Thread Edward Diener
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. ---

Re: [Valgrind-users] Valgrind on arm system startup message

2018-06-29 Thread Edward Diener
t permission denied. On 6/28/18, Edward Diener wrote: I am attempting to use Valgrind with an application on an embedded arm system. Debugging with gdb, a problem is occurring with a shared library used by the application, where gdb is showing a SIGABRT from a malloc call in a well-supported

Re: [Valgrind-users] Valgrind on arm system startup message

2018-06-29 Thread Edward Diener
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

[Valgrind-users] Valgrind on arm system startup message

2018-06-28 Thread Edward Diener
I am attempting to use Valgrind with an application on an embedded arm system. Debugging with gdb, a problem is occurring with a shared library used by the application, where gdb is showing a SIGABRT from a malloc call in a well-supported library, but can not show me the memory overwrite proble