https://bugs.kde.org/show_bug.cgi?id=422174
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@klomp.org
--- Comment #1 from Mark Wielaard <m...@klomp.org> ---
(In reply to Tom Deseyn from comment #0)
> When running .NET Core 3.1 applications under valgrind I get SIGILL for
>
> vex amd64->IR: unhandled instruction bytes: 0x48 0xE9 0x70 0xB3 0x41 0xA9
> 0x49 0xBA 0x88 0xCD
> vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0
> vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
> vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
This is tricky. This looks like a jmp instruction followed by some noise. It
might be that something went wrong earlier and we are now looking at some bad
data.
Since this is a JIT could you try running with --smc-check=all which will make
valgrind more aggressively look when it needs to update its code translations.
Also could you show a bit more info on how you precisely run valgrind, which
options you used, etc. Are there any other warnings? Could you run with -v and
post the full output here?
--
You are receiving this mail because:
You are watching all bug changes.
