https://bugs.kde.org/show_bug.cgi?id=396001
John Reiser <jrei...@bitwagon.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from John Reiser <jrei...@bitwagon.com> ---
OK, it's the same as #344802. It would be nice to fix a bug that is 2.5 to 3
years old, depending on how you count. Anyone who uses libcrypto.so.1.1 on ARM
will stumble on this bug.
The [valgrind-users] report "Valgrind on arm system startup message" of Thu, 28
Jun 2018 20:21:05 -0400 gives some distracting information:
=====
==621== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==621== Command: ./myprogram
==621==
disInstr(thumb): unhandled instruction: 0xEC51 0x0F1E
==621== valgrind: Unrecognised instruction at address 0x4cc1767.
==621== at 0x4CC1766: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1)
=====
Notice that it says "thumb", with a not-even PC address 0x4cc1767, and that the
disassembly is two 16-bit words instead of one 32-bit word. Fooled me.
*** This bug has been marked as a duplicate of bug 344802 ***
--
You are receiving this mail because:
You are watching all bug changes.
