IR: unimplemented insn: B348 0010 on s390x in apt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
valgrind (Ubuntu) |
Fix Released
|
Undecided
|
Julian Andres Klode |
Bug Description
apt's autopkgtest triggers a Valgrind error:
http://
Test for successful execution of valgrind aptget update -o Acquire:
==203867== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==203867== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==203867== Command: /usr/bin/apt-get update -o Acquire:
==203867==
vex s390->IR: unimplemented insn: B348 0010
==203867== valgrind: Unrecognised instruction at address 0x4ba27f6.
==203867== at 0x4BA27F6: std::__
==203867== by 0x4985DAB: ReadConfigFile(
==203867== by 0x4A218D9: pkgInitConfig(
==203867== by 0x486801D: ParseCommandLin
==203867== by 0x10BE3B: main (in /usr/bin/apt-get)
==203867== Your program just tried to execute an instruction that Valgrind
==203867== did not recognise. There are two possible reasons for this.
==203867== 1. Your program has a bug and erroneously jumped to a non-code
==203867== location. If you are running Memcheck and you just saw a
==203867== warning about a bad jump, it's probably your program's fault.
==203867== 2. The instruction is legitimate but Valgrind doesn't handle it,
==203867== i.e. it's Valgrind's fault. If you think this is the case or
==203867== you are not sure, please let us know and we'll try to fix it.
==203867== Either way, Valgrind will now raise a SIGILL signal which will
==203867== probably kill your program.
==203867==
==203867== Process terminating with default action of signal 4 (SIGILL)
==203867== Illegal opcode at address 0x4BA27F6
==203867== at 0x4BA27F6: std::__
==203867== by 0x4985DAB: ReadConfigFile(
==203867== by 0x4A218D9: pkgInitConfig(
==203867== by 0x486801D: ParseCommandLin
==203867== by 0x10BE3B: main (in /usr/bin/apt-get)
==203867==
==203867== HEAP SUMMARY:
==203867== in use at exit: 84,929 bytes in 866 blocks
==203867== total heap usage: 4,880 allocs, 4,014 frees, 438,639 bytes allocated
==203867==
==203867== LEAK SUMMARY:
==203867== definitely lost: 0 bytes in 0 blocks
==203867== indirectly lost: 0 bytes in 0 blocks
==203867== possibly lost: 0 bytes in 0 blocks
==203867== still reachable: 84,929 bytes in 866 blocks
==203867== suppressed: 0 bytes in 0 blocks
==203867== Rerun with --leak-check=full to see details of leaked memory
==203867==
==203867== For lists of detected and suppressed errors, rerun with: -s
==203867== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction (core dumped)
FAIL: exitcode 132
...
summary: |
- IR: unimplemented insn: B348 0010 on s390x + IR: unimplemented insn: B348 0010 on s390x in apt |
Changed in valgrind (Ubuntu): | |
status: | New → Fix Committed |
assignee: | nobody → Julian Andres Klode (juliank) |
This bug was fixed in the package valgrind - 1:3.15.0-1ubuntu7
---------------
valgrind (1:3.15.0-1ubuntu7) focal; urgency=medium
* Cherry pick upstream commit Bug 416301 - s390x: Support
"compare and signal" instructions (LP: #1862183)
-- Julian Andres Klode <email address hidden> Thu, 06 Feb 2020 15:49:24 +0100