[Bug 28735] New: ntdll/tests/exception.ok fails under valgrind

http://bugs.winehq.org/show_bug.cgi?id=28735

Bug #: 28735
           Summary: ntdll/tests/exception.ok fails under valgrind
           Product: Wine
           Version: 1.3.30
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

Running "make exception.ok" in ntdll/tests under valgrind fails.
This has been happening since at least early last year.  Log:

valgrind: Unrecognised instruction at address 0x7f230000.
Your program just tried to execute an instruction that Valgrind
did not recognise.  There are two possible reasons for this.
1. Your program has a bug and erroneously jumped to a non-code
   location.  If you are running Memcheck and you just saw a
   warning about a bad jump, it's probably your program's fault.
2. The instruction is legitimate but Valgrind doesn't handle it,
   i.e. it's Valgrind's fault.  If you think this is the case or
   you are not sure, please let us know and we'll try to fix it.
Either way, Valgrind will now raise a SIGILL signal which will
probably kill your program.
err:seh:segv_handler Got unexpected trap 0
exception.c:396: Test failed: 15: Wrong exception code c000001d/c0000005
exception.c:399: Test failed: 15: Wrong exception address 0x7f230000/0x7f230006
exception.c:405: Test failed: 15: Wrong number of parameters 0/2
exception.c:396: Test failed: 15: Wrong exception code c000001d/c0000005
exception.c:399: Test failed: 15: Wrong exception address 0x7f230000/0x7f230006
exception.c:405: Test failed: 15: Wrong number of parameters 0/2
Conditional jump or move depends on uninitialised value(s)
   at handler (exception.c:418)
   by ??? (signal_i386.c:2522)
   by ??? (signal_i386.c:2522)
   by __regs_RtlUnwind (signal_i386.c:2397)
   by __wine_call_from_regs (in dlls/ntdll/ntdll.dll.so)
   by ??? (signal_i386.c:2413)
   by unwind_frame (exception.c:74)
   by __wine_exception_handler (exception.c:99)
   by ??? (signal_i386.c:2522)
   by ??? (signal_i386.c:2522)
   by call_stack_handlers (signal_i386.c:616)
   by raise_exception (signal_i386.c:694)
   by NtRaiseException (signal_i386.c:2422)
   by raise_segv_exception (signal_i386.c:1751)
   by 0xDEADBABD: ???
   by func_exception (exception.c:465)
   by run_test (test.h:556)
   by main (test.h:624)
 Uninitialised value was created by a client request
   at setup_exception_record (signal_i386.c:1629)
   by segv_handler (signal_i386.c:1876)
   by ??? (in /lib/i386-linux-gnu/libpthread-2.13.so)

Might be a valgrind bug, but winehq is probably the right place for triaging
it.