[Bug 20799] Mirror's Edge freezes during startup

wine-bugs at winehq.org wine-bugs at winehq.org
Sat Mar 20 19:51:39 CDT 2010


--- Comment #46 from Wylda <wylda at volny.cz>  2010-03-20 19:51:38 ---
Created an attachment (id=26939)
 --> (http://bugs.winehq.org/attachment.cgi?id=26939)
Unreal tournament under Valgrind

Advantage of UT3 is, that it is able to run under valgrind. Attached is output

WINEDEBUG=+dsalsa valgrind --trace-children=yes
--suppressions=$HOME/valgrind-suppressions wine UT3.exe 2>&1 | tee out3.txt

Would it help to rerun with --error-limit=no or with other parametr?

Note: The "Unrecognised instruction" is different on each run...

fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to
trace:dsalsa:widDsCreate (0,0x7f02f2f4)
trace:dsalsa:IDsCaptureDriverImpl_GetDriverDesc (0x7f020200,0x7f02f2f8)
trace:dsalsa:IDsCaptureDriverImpl_Open Success
trace:dsalsa:IDsCaptureDriverImpl_GetCaps (0x7f020200,0x7f02f524)
trace:dsalsa:IDsCaptureDriverBufferImpl_SetFormat (0x7f0564a8, 0x7f055e90)
trace:dsalsa:CreateMMAP mmap'd buffer is an ALSA type 14 buffer
trace:dsalsa:CreateMMAP format=S16_LE  frames=2730  channels=1 
bits_per_sample=16  bits_per_frame=16
vex x86->IR: unhandled instruction bytes: 0x8F 0x1F 0xB9 0xB
==27570== valgrind: Unrecognised instruction at address 0xc4b4170.
==27570== Your program just tried to execute an instruction that Valgrind
==27570== did not recognise.  There are two possible reasons for this.
==27570== 1. Your program has a bug and erroneously jumped to a non-code
==27570==    location.  If you are running Memcheck and you just saw a
==27570==    warning about a bad jump, it's probably your program's fault.
==27570== 2. The instruction is legitimate but Valgrind doesn't handle it,
==27570==    i.e. it's Valgrind's fault.  If you think this is the case or
==27570==    you are not sure, please let us know and we'll try to fix it.
==27570== Either way, Valgrind will now raise a SIGILL signal which will
==27570== probably kill your program.
err:seh:segv_handler Got unexpected trap 0
fixme:dbghelp:validate_addr64 Unsupported address ffffffff81160000
fixme:dbghelp:validate_addr64 Unsupported address ffffffff81290000
fixme:faultrep:ReportFault 0x7f43cbec 0x0 stub
AL lib: ALc.c:1822: alcCloseDevice(): deleting 32 Filter(s)
wine: Unhandled page fault on read access to 0x00000000 at address 0xac9371
(thread 001c), starting debugger...

Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the wine-bugs mailing list