Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-3229

Valgrind fails on aws-build-test with Illegal Instruction

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Trivial - P5
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage 2017-05-08

      Description

      Valgrind fails with the following error on the aws-build-test machine in Jenkins:

      ==23199== Memcheck, a memory error detector
      ==23199== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
      ==23199== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
      ==23199== Command: ./examples/c/ex_all
      ==23199==
      vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x1B 0x4 0x24 0x66 0xF 0x1B
      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.nVVVV=0x0 ESC=0F
      vex amd64->IR:   PFX.66=1 PFX.F2=0 PFX.F3=0
      ==23199== valgrind: Unrecognised instruction at address 0x4015237.
      ==23199==    at 0x4015237: _dl_runtime_resolve (in /lib64/ld-2.17.so)
      ==23199==    by 0x41C820: ??? (in /bin/bash)
      ==23199==    by 0xFFF000137: ???
      ==23199==    by 0x1B: ???
      ==23199==    by 0x1: ???
      ==23199==    by 0xFFF0003DE: ???
      ==23199==    by 0xFFF0003E6: ???
      ==23199== Your program just tried to execute an instruction that Valgrind
      ==23199== did not recognise.  There are two possible reasons for this.
      ==23199== 1. Your program has a bug and erroneously jumped to a non-code
      ==23199==    location.  If you are running Memcheck and you just saw a
      ==23199==    warning about a bad jump, it's probably your program's fault.
      ==23199== 2. The instruction is legitimate but Valgrind doesn't handle it,
      ==23199==    i.e. it's Valgrind's fault.  If you think this is the case or
      ==23199==    you are not sure, please let us know and we'll try to fix it.
      ==23199== Either way, Valgrind will now raise a SIGILL signal which will
      ==23199== probably kill your program.
      

      It only appears to fail on that machine, so I am removing it from the set of servers that valgrind can run on until we fix

        Attachments

          Activity

            People

            Assignee:
            david.hows David Hows
            Reporter:
            david.hows David Hows
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: