https://bugs.kde.org/show_bug.cgi?id=381819
Erik Zscheile <zseri.de...@ytrizja.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zseri.de...@ytrizja.de
--- Comment #22 from Erik Zscheile <zseri.de...@ytrizja.de> ---
I just ran into exactly this error. With the exact same "unhandled instruction
bytes: 0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4 0x0 0x0 0x89" with valgrind-3.16.1,
glibc-2.32-r2, gcc-9.3.0-r1 on AMD A10-5800K APU. As this makes valgrind
unusable for many programs (e.g. almost everything that uses glibc with dynamic
linking, at least), it would be extremely nice to integrate a patch for this
into the upstream valgrind repo, to avoid the regular catch-up. I think it
would be enough to just fix the common instrs issued by GCC when compiling
glibc, as this would probably cover most programs.
Side question: Is there a way to prevent gcc from issuing the 'bextr' instr,
while allowing optimization (-O2)? I would be able to recompile glibc to make
it work with valgrind, but I don't what must be adjusted.
--
You are receiving this mail because:
You are watching all bug changes.
