Am 29.06.2023 um 18:19 schrieb Mark Wielaard:
Hi Simon,
On Thu, Jun 29, 2023 at 05:46:59PM +0200, Simon Sobisch wrote:
Am 29.06.2023 um 15:10 schrieb John Reiser:
Running valgrind on GnuCOBOL errors out with
vex amd64->IR: unhandled instruction bytes:
0x62 0xF1 0xFE 0x8 0x6F 0x7 0x48
Hi Simon,
On Thu, Jun 29, 2023 at 05:46:59PM +0200, Simon Sobisch wrote:
> Am 29.06.2023 um 15:10 schrieb John Reiser:
> >>Running valgrind on GnuCOBOL errors out with
> >>
> >>vex amd64->IR: unhandled instruction bytes:
> >> 0x62 0xF1 0xFE 0x8 0x6F 0x7 0x48 0xC7 0x5 0x6F
> >>vex amd64->IR:
Sorry, I should have made this explicit!
The error initially was seen with
$> valgrind --version
valgrind-3.20.0
which was then updated to
$> valgrind --version
valgrind-3.21.0
where this output below (100% identical to 3.20.0) came from.
Both Valgrind and GnuCOBOL were compiled wit
Running valgrind on GnuCOBOL errors out with
vex amd64->IR: unhandled instruction bytes:
0x62 0xF1 0xFE 0x8 0x6F 0x7 0x48 0xC7 0x5 0x6F
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
va
Running valgrind on GnuCOBOL errors out with
vex amd64->IR: unhandled instruction bytes:
0x62 0xF1 0xFE 0x8 0x6F 0x7 0x48 0xC7 0x5 0x6F
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
val