https://bugs.kde.org/show_bug.cgi?id=400538
Austin English <austinengl...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |austinengl...@gmail.com
--- Comment #7 from Austin English <austinengl...@gmail.com> ---
Okay, I can reproduce this, it needs a couple more valgrind arguments.
# First, start a wine process (so that wineserver is running before valgrind
starts):
$ wine64 start /min winemine
# Then, start notepad under valgrind:
$ austin@laptop:~/src/valgrind$ valgrind --trace-children=yes
--vex-iropt-register-updates=allregs-at-mem-access
/opt/oldwow64/wine-4.5/bin/wine64 notepad
==2874== Memcheck, a memory error detector
==2874== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2874== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==2874== Command: /opt/oldwow64/wine-4.5/bin/wine64 notepad
==2874==
==2874== Memcheck, a memory error detector
==2874== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2874== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==2874== Command: /opt/oldwow64/wine-4.5/bin/wine64-preloader
/opt/oldwow64/wine-4.5/bin/wine64 notepad
==2874==
preloader: Warning: failed to reserve range 0000000000110000-0000000068000000
==2874==
vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2
0xCC 0x90 0x55
vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2
0xCC 0x90 0x55
vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==2874== valgrind: Unrecognised instruction at address 0x7bc9bff3.
==2874== at 0x7BC9BFF3: ??? (in
/opt/oldwow64/wine-4.5/lib64/wine/ntdll.dll.so)
==2874== by 0x7BC9C0CA: ??? (in
/opt/oldwow64/wine-4.5/lib64/wine/ntdll.dll.so)
==2874== Your program just tried to execute an instruction that Valgrind
==2874== did not recognise. There are two possible reasons for this.
==2874== 1. Your program has a bug and erroneously jumped to a non-code
==2874== location. If you are running Memcheck and you just saw a
==2874== warning about a bad jump, it's probably your program's fault.
==2874== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2874== i.e. it's Valgrind's fault. If you think this is the case or
==2874== you are not sure, please let us know and we'll try to fix it.
==2874== Either way, Valgrind will now raise a SIGILL signal which will
==2874== probably kill your program.
005d:err:seh:segv_handler Got unexpected trap 0
==2874== Invalid write of size 8
==2874== at 0x7BC9BFF8: ??? (in
/opt/oldwow64/wine-4.5/lib64/wine/ntdll.dll.so)
==2874== by 0x7BC9BFF2: ??? (in
/opt/oldwow64/wine-4.5/lib64/wine/ntdll.dll.so)
==2874== by 0x7BC9C0CA: ??? (in
/opt/oldwow64/wine-4.5/lib64/wine/ntdll.dll.so)
==2874== Address 0x7ffffe20f4b8 is in a rw- anonymous segment
==2874==
005d:err:seh:NtRaiseException Unhandled exception code c000001d flags 0 addr
0x7bc9bff3
==2874==
==2874== HEAP SUMMARY:
==2874== in use at exit: 731,905 bytes in 6,501 blocks
==2874== total heap usage: 13,837 allocs, 7,336 frees, 2,963,926 bytes
allocated
==2874==
==2874== LEAK SUMMARY:
==2874== definitely lost: 318 bytes in 2 blocks
==2874== indirectly lost: 0 bytes in 0 blocks
==2874== possibly lost: 0 bytes in 0 blocks
==2874== still reachable: 731,587 bytes in 6,499 blocks
==2874== suppressed: 0 bytes in 0 blocks
==2874== Rerun with --leak-check=full to see details of leaked memory
==2874==
==2874== For counts of detected and suppressed errors, rerun with: -v
==2874== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Tested with 3.15-rc1 / wine-4.5
--
You are receiving this mail because:
You are watching all bug changes.
