Am Dienstag, 10. April 2007 12:46 schrieb Stefan Dösinger:
> > attached you find the trace. I am wondering why it so much smaller. I was
> > also able to get a proper callstack of the crash.
> You didn't set the trace flags properly. Maybe you misspelled WINEDEBUG ?
> However, according to the cra
> attached you find the trace. I am wondering why it so much smaller. I was
> also able to get a proper callstack of the crash.
You didn't set the trace flags properly. Maybe you misspelled WINEDEBUG ?
However, according to the crash dump it crashes in the 3D driver, which is
rather suspicious. I
Am Montag, 9. April 2007 23:09 schrieb Klaus Layer:
> Am Sonntag, 8. April 2007 01:14 schrieb Vitaliy Margolen:
> > Do not strip Wine when you debuggin it, _especially_ when you sending
> > your traces to wine-devel.
> >
> > Properly compiling Wine would help. This is invalid. Please visit wiki
>
Am Sonntag, 8. April 2007 01:14 schrieb Vitaliy Margolen:
> Do not strip Wine when you debuggin it, _especially_ when you sending
> your traces to wine-devel.
>
> Properly compiling Wine would help. This is invalid. Please visit wiki
> page(s) for gentoo that state which flags you should and which
Am Sonntag, 8. April 2007 12:55 schrieben Sie:
> Hi,
> Interestingly this application does nothing that would make ddraw return a
> failure. Can you send a ddraw,d3d7 trace WITH the registry key set as a
> reference?
>
> As far as I can see, this application is on its way to set up a Direct3D
>
Klaus Layer wrote:
> 21 0x7ee5050f in kernel32 (+0x5050f) (0x0034ffe8)
Do not strip Wine when you debuggin it, _especially_ when you sending
your traces to wine-devel.
> 22 0xb7ec8397 (0x)
> 0x7e42f2e9: movzbl 0xfffe(%ecx),%edx
> Modules:
> Module Address Debu
> I created the key, but with it wine crashes with the dump below. I
> therefore removed the key and recorded a +ddraw,+d3d7 trace I will send
> separately to you.
Looks like this crash is unrelated to the original issue. The key worked
around the first issue, now we have another one of which I ha
low is the post mortem trace. Can anyone give me a hint
> > > > what can be done?
> > > >
> > > > err:ddraw:IDirectDrawImpl_QueryInterface (0x1bdd28) The App is
> > > > requesting
> >
> > a
&
gt; > > what can be done?
> > >
> > > err:ddraw:IDirectDrawImpl_QueryInterface (0x1bdd28) The App is
> > > requesting
>
> a
>
> > > D3D device, but a non-OpenGL surface type was choosen. Prepare for
>
> trouble!
>
> > > err:ddraw:IDirectDrawIm
Am Samstag, 7. April 2007 14:01 schrieb Stefan Dösinger:
> > when running an educational game, wine crashed and asked me to contact
> > wine-devel. Below is the post mortem trace. Can anyone give me a hint what
> > can be done?
>
> > err:ddraw:IDirectDrawImpl_QueryInte
> when running an educational game, wine crashed and asked me to contact
> wine-devel. Below is the post mortem trace. Can anyone give me a hint what
> can be done?
> err:ddraw:IDirectDrawImpl_QueryInterface (0x1bdd28) The App is requesting a
> D3D device, but a non-OpenGL s
ureMem (0x1be928) : stub,
simulating 64MB for now, returning 64MB
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x1bdd28)->(0x10026,0011)
fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 32 to
8
err:ddraw:IDirectDrawImpl_QueryInterface (0x1bdd28) The App is req
12 matches
Mail list logo
