======================================
   IDSgrep 0.7pre: ./test-suite.log
======================================

# TOTAL: 25
# PASS:  24
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test/vgneko
=================

./test/vgneko: line 19: 18066 Illegal instruction     valgrind --leak-check=full ./idsgrep '&!⿰?畏&⿰?*⿱?田...⺨' *.eids 2> vgneko-out.$$
==18066== Memcheck, a memory error detector
==18066== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==18066== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==18066== Command: ./idsgrep &!⿰?畏&⿰?*⿱?田...⺨ chise.eids cjkvi-j.eids edict.eids kanjivg.eids tsukurimashou.eids vgneko-in.18061.eids
==18066== 
==18066== Conditional jump or move depends on uninitialised value(s)
==18066==    at 0x402A9FE: ??? (in /lib64/ld-linux-x86-64-2.42.so)
==18066==    by 0x6C2F62696C2F6C60: ???
==18066==    by 0x6F732E6464626268: ???
==18066==    by 0x302D: ???
==18066==    by 0x300000005: ???
==18066==    by 0x40178EB: ??? (in /lib64/ld-linux-x86-64-2.42.so)
==18066==    by 0x6C2F343662696C2E: ???
==18066==    by 0x732E657263706268: ???
==18066==    by 0x7FF: ???
==18066==    by 0x2C0F4: ???
==18066== 
--18066-- WARNING: unhandled amd64-linux syscall: 334
--18066-- You may be able to write your own handler.
--18066-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--18066-- Nevertheless we consider this a bug.  Please report
--18066-- it at http://valgrind.org/support/bug_reports.html.
vex amd64->IR: unhandled instruction bytes: 0xF3 0xF 0x1E 0xFA 0x48 0x8B 0x35 0x2D
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=0 PFX.F2=0 PFX.F3=1
==18066== valgrind: Unrecognised instruction at address 0x49cf590.
==18066==    at 0x49CF590: ??? (in /usr/lib64/libgcc_s.so.1)
==18066==    by 0x400633D: ??? (in /lib64/ld-linux-x86-64-2.42.so)
==18066==    by 0x37: ???
==18066==    by 0x7: ???
==18066==    by 0xFFEFFFF77: ???
==18066==    by 0xFFEFFFFBF: ???
==18066==    by 0x403B2EF: ???
==18066==    by 0x4006442: ??? (in /lib64/ld-linux-x86-64-2.42.so)
==18066== Your program just tried to execute an instruction that Valgrind
==18066== did not recognise.  There are two possible reasons for this.
==18066== 1. Your program has a bug and erroneously jumped to a non-code
==18066==    location.  If you are running Memcheck and you just saw a
==18066==    warning about a bad jump, it's probably your program's fault.
==18066== 2. The instruction is legitimate but Valgrind doesn't handle it,
==18066==    i.e. it's Valgrind's fault.  If you think this is the case or
==18066==    you are not sure, please let us know and we'll try to fix it.
==18066== Either way, Valgrind will now raise a SIGILL signal which will
==18066== probably kill your program.
==18066== 
==18066== Process terminating with default action of signal 4 (SIGILL)
==18066==  Illegal opcode at address 0x49CF590
==18066==    at 0x49CF590: ??? (in /usr/lib64/libgcc_s.so.1)
==18066==    by 0x400633D: ??? (in /lib64/ld-linux-x86-64-2.42.so)
==18066==    by 0x37: ???
==18066==    by 0x7: ???
==18066==    by 0xFFEFFFF77: ???
==18066==    by 0xFFEFFFFBF: ???
==18066==    by 0x403B2EF: ???
==18066==    by 0x4006442: ??? (in /lib64/ld-linux-x86-64-2.42.so)
==18066== 
==18066== HEAP SUMMARY:
==18066==     in use at exit: 0 bytes in 0 blocks
==18066==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==18066== 
==18066== All heap blocks were freed -- no leaks are possible
==18066== 
==18066== For counts of detected and suppressed errors, rerun with: -v
==18066== Use --track-origins=yes to see where uninitialised values come from
==18066== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
FAIL test/vgneko (exit status: 1)