"Peter Hunnisett" <[EMAIL PROTECTED]> writes:
> >So maybe the application does not expect a DDraw implementation not to
> >support D3D2 and crash for this...
>
> My guess is that it's expecting the 3d2 interface because of some other ddraw
> component being available. That's to say, buggy application code.
>
> To test that theory, you could modify the Xlib_IDirectDraw2Impl_QueryInterface
> code to return 0xDEADABBA or something like that and see if the crash promptly
> happens on that address (since it crashes on NULL which is what the object
> should be set to on failure from that routine).
After one minute looking at the source this morning I can see that
HAVE_OPENGL is not set, but I tested this anyway to put the blame
where it belongs. ABBA is not dead yet though, so I killed a FADE
instead. It promptly crashes on 0xDEADFADE as you say.
--
Peter Bortas http://peter.bortas.org
Roxen IS http://www.roxen.com
