[Bug 16516] New: Space Giraffe: Unhandled page fault on read access to 0x00000000

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

Summary: Space Giraffe: Unhandled page fault on read access to
                    0x00000000
           Product: Wine
           Version: 1.1.9
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=17955)
 --> (http://bugs.winehq.org/attachment.cgi?id=17955)
Backtrace

I'm trying to run Jeff Minter's Space Giraffe demo (which is available at
http://www.llamasoft.co.uk/downloads/SpaceGiraffe.exe at time of writing)

The install seemed to go OK. I had to add d3dx9_38.dll to my system32
directory, and an override for opengl in winecfg in order to get the
game to start at all. After selecting my language, I get an error
dialog (from the game, not Wine, I think) saying:

Some unsupported/different feature been detected
        This may lead to some incompatibility and/or performance penalty
        or worse not to work at all.

Then I get another dialog:

Can't initialise XACT engine !

and then the game crashes with an unhandled page fault error. Whether
Wine is at fault, or just buggy error handling code in the game is
another matter, of course. Either way, the game isn't playable under
Wine :-(

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

Christian Costa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Christian Costa   2008-12-16 04:22:32 ---

The log says :

err:ole:CoGetClassObject class {962f5027-99be-4692-a468-85802cf8de61} not
registered
err:ole:CoGetClassObject no class object {962f5027-99be-4692-a468-85802cf8de61}
could be created for context 0x1

Search on the net gives this :

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{962f5027-99be-4692-a468-
85802cf8de61}\InProcServer32] ADD @="C:\WINDOWS\system32\xactengine3_1.dll"

which refers to a dll of the XACT engine.

It seems the demo did not install correctly because this entry is missing.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

ricardo filipe  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from ricardo filipe   2009-01-28 09:38:56 ---
it seems it's another one of the directx dlls missing...

XACTEngine, XAudio2, X3DAudio and XAPOFX families DLLs all seem to not be in
wine.

d3dx9_38.dll is not needed native anymore, but you could try getting the xact
dlls from native and see if it works.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

Alex Bennee  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Alex Bennee   2009-07-28 10:20:25 ---
The crash seems to have moved on but running the demo does generate a bunch of
d3d:fixme messages:

16:12 alex@danny/x86_64 [wine.git] >wine ~/.wine/drive_c/Program\
Files/SpaceGiraffe/SpaceGiraffePC.exe
Could not load wine-gecko. HTML rendering will be disabled.
wine: configuration in '/home/alex/.wine' has been updated.
fixme:keyboard:RegisterHotKey (0x120030,0,0x00000001,9): stub
fixme:d3d:check_fbo_compat Format WINED3DFMT_R8G8B8 with rendertarget flag is
not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_A8R8G8B8 with rendertarget flag is
not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_X8R8G8B8 with rendertarget flag is
not supported as FBO color attachment, and no fallback specified.
fixme:d3d:check_fbo_compat Format WINED3DFMT_R5G6B5 rtInternal format is not
supported as FBO color attachment.
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM rtInternal format is
not supported as FBO color attachment.
fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16B16A16_UNORM with
rendertarget flag is not supported as FBO color attachment, and no fallback
specified.
fixme:win:EnumDisplayDevicesW ((null),0,0x32e870,0x00000000), stub!
fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to
SetDepthStencilSurface
fixme:d3d:debug_fbostatus Unrecognied FBO status 0x00000000
fixme:d3d:context_check_fbo_status FBO status unrecognized (0)wine: Unhandled
page fault on read access to 0x00000008 at address 0x7ec02dfc (thread 0009),
starting debugger...

I assume the actual crash is probably an untested fall-through case in the
original code.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

--- Comment #4 from Henri Verbeet   2009-07-28 14:06:01 ---
(In reply to comment #3)
> fixme:d3d:debug_fbostatus Unrecognied FBO status 0x00000000
> fixme:d3d:context_check_fbo_status FBO status unrecognized (0)

Which driver are you using? Mesa?
0 is not a valid return value for glCheckFramebufferStatus(), you'll want to
report that to your driver vendor if it still happens with current versions of
the driver. The crash probably happens because the driver returns 0 while
rendering onscreen as well, which would result in dereferencing
context->current_fbo while it's NULL.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

--- Comment #5 from Alex Bennee   2009-07-29 02:15:35 ---
(In reply to comment #4)
> (In reply to comment #3)
> > fixme:d3d:debug_fbostatus Unrecognied FBO status 0x00000000
> > fixme:d3d:context_check_fbo_status FBO status unrecognized (0)
>
> Which driver are you using? Mesa?
> 0 is not a valid return value for glCheckFramebufferStatus(), you'll want to
> report that to your driver vendor if it still happens with current versions of
> the driver. The crash probably happens because the driver returns 0 while
> rendering onscreen as well, which would result in dereferencing
> context->current_fbo while it's NULL.

I'm currently running:

x11-drivers/xf86-video-intel-2.8.0
media-libs/mesa-7.5-r2

On top of Gnome/Compiz

I'm afraid I'm not really familiar with OpenGL and rendering but if you can
point me to any simple tutorial/test cases that use glCheckFramebufferStatus I
can give them a spin on the native setup.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

--- Comment #6 from Alex Bennee   2009-08-05 02:50:44 ---
(In reply to comment #4)
> (In reply to comment #3)
> > fixme:d3d:debug_fbostatus Unrecognied FBO status 0x00000000
> > fixme:d3d:context_check_fbo_status FBO status unrecognized (0)
>
> Which driver are you using? Mesa?
> 0 is not a valid return value for glCheckFramebufferStatus(), you'll want to
> report that to your driver vendor if it still happens with current versions of
> the driver. The crash probably happens because the driver returns 0 while
> rendering onscreen as well, which would result in dereferencing
> context->current_fbo while it's NULL.

Ok I created a simple test program to check Mesa. Running that I can see
glCheckFramebufferStatus() behaving as it should (returning
GL_FRAMEBUFFER_COMPLETE 0x8CD5). Is there any way I can dump all the OpenGL
commands generated while running wine to see if I can regenerate the failure
mode?

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

--- Comment #7 from Henri Verbeet   2009-08-05 02:59:47 ---
Did you compile that with -m32? (I'm assuming you're on AMD64 basaed on your
hostname.)

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

--- Comment #8 from Alex Bennee   2009-08-11 14:09:34 ---
(In reply to comment #7)
> Did you compile that with -m32? (I'm assuming you're on AMD64 basaed on your
> hostname.)

My bad. The test case won't compile under -m32, funnily enough failing to find
glCheckFramebufferStatus. I'm currently examining Gentoo's 32 bit emulation
libraries for AMD64

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

Jaroslav Zeman  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Jaroslav Zeman   2009-09-11 08:51:32 ---
I have same bug as Alex, but it seems to do this with all d3d games. In
Rollercoaster tycoon 3 it shows some these errors:

fixme:d3d:check_fbo_compat Format WINED3DFMT_R8G8B8 with rendertarget flag is
not supported as FBO color attachment, and no fallback specified.

then it shows dialog: Your graphic hardware or drivers do not meet the minimum
requiments to run RCT3.
(I am sure I meet these requiments)

and then it shows
fixme:win:EnumDisplayDevicesW ((null),0,0x33f39c,0x00000000), stub!
and crashes.

I have searched it at internet and it looks this happens with Intel graphics
and maybe with x86_64 system. Maybe the problem is at Intel's drivers.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

--- Comment #10 from Austin English  2011-08-16 22:02:06 CDT ---
4bdbf8296b427160c03f190500e376936da42cd3  SpaceGiraffeSetup.exe
is available from http://lsshop.s3.amazonaws.com/SpaceGiraffeSetup.exe, and
works fine.

The original link is still alive, but fails to install for me, saying it fails
its checksum verification.

Please retest in 1.3.26.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

--- Comment #11 from Tethys  2011-08-17 09:16:57 CDT ---
Created an attachment (id=36011)
 --> (http://bugs.winehq.org/attachment.cgi?id=36011)
Backtrace

The latest wine for my distribution (Fedora 15) is 1.3.24, which still
shows the problem. Updated backtrace attached. If necessary, I could
probably compile up a version of 1.3.26, but it's a work machine, so
I don't have much opportunity to mess around with it.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

Tethys  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.1.9                       |1.3.24

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000

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

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.3.24                      |1.1.9

--- Comment #12 from Juan Lang  2011-08-17 11:11:00 CDT ---
Please don't change the originally reported version, a comment is enough.

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000 (missing XAudio2 component registration in 64-bit WINEPREFIX)

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

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                URL|                            |http://lsshop.s3.amazonaws.
                   |                            |com/SpaceGiraffeSetup.exe
           Platform|Other                       |x86-64
                 CC|                            |[e-mail]
         Resolution|                            |DUPLICATE
            Summary|Space Giraffe: Unhandled    |Space Giraffe: Unhandled
                   |page fault on read access   |page fault on read access
                   |to 0x00000000               |to 0x00000000 (missing
                   |                            |XAudio2 component
                   |                            |registration in 64-bit
                   |                            |WINEPREFIX)
           Severity|enhancement                 |normal

--- Comment #13 from Anastasius Focht  2013-04-27 05:53:19 CDT ---
Hello folks,

--- quote ---
err:ole:CoGetClassObject class {e21a7345-eb21-468e-be50-804db97cf708} not
registered
err:ole:CoGetClassObject no class object {e21a7345-eb21-468e-be50-804db97cf708}
could be created for context 0x1
wine: Unhandled page fault on read access to 0x00000000 at address 0x447a34
(thread 0009), starting debugger...
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x00447a34).
....
process  tid      prio (all id:s are in hex)
00000008 (D) C:\Program Files (x86)\SpaceGiraffe\SpaceGiraffePC.exe
        00000009    0 <==
--- quote ---

Missing XAudio2 COM inproc server registration/keys when installing in 64-bit
prefix with default Winver 'Windows XP' is intended, there is nothing to fix
here.

I explained everything in bug 30912

Use WinVer > Windows XP when you intend to install XAudio2 in 64-bit prefix or
use 32-bit prefix.

Regards

*** This bug has been marked as a duplicate of bug 30912 ***

[Bug 16516] Space Giraffe: Unhandled page fault on read access to 0x00000000 (missing XAudio2 component registration in 64-bit WINEPREFIX)

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #14 from Austin English  2013-04-29 03:25:04 CDT ---
Closing.