wine users - May 2011 - Help needed troubleshooting page fault in wine

I'm trying to troubleshoot  a game crash under Wine. Here's a snippet
from the log file created under Wine 1.3.20:


Code:
wine: Unhandled page fault on read access to 0x00000000 at address 0x44a179
(thread 0022), starting debugger...
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0044a179).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:0044a179 ESP:0033fcd4 EBP:000001a0 EFLAGS:00010246(  R- --  I  Z- -P- )
 EAX:00000000 EBX:00000000 ECX:0000000f EDX:00000000
 ESI:0088555c EDI:00885520
Stack dump:
0x0033fcd4:  00000020 00000020 000001a0 00000240
0x0033fce4:  00a693f0 004f2173 0044a396 00000000
0x0033fcf4:  00000000 004d3efe 00000000 00000006
0x0033fd04:  00000006 3cc67e58 0089c1d0 0089c200
0x0033fd14:  7eb5a800 004d4141 00000000 7eb61b70
0x0033fd24:  0033fe90 0089c1c0 7eb5a8a0 3cc67e58
Backtrace:
0x0044a179: cmpw	%bx,0x0(%eax)



I don't have a clue what is causing the crash. With the above information is
there anything I can do to determine if this is an issue with Wine? I just did a
fresh install of the new Ubuntu (64 bit) release last week so I have a
relatively clean environment. It might be distro related but honestly I
can't tell either way at this point.

Can anyone tell me what's happening at 0x0044a179?

On Wed, May 18, 2011 at 1:40 PM, dk <wineforum-user at winehq.org>
wrote:
> I'm trying to troubleshoot ?a game crash under Wine. Here's a
snippet from the log file created under
> Wine 1.3.20:
>
Not a clue and cannot even begin to help given the information you provided.

1.  Linux Distribution and Version.
2.  What is the name of the Program you are running.
3.  Video card and driver version.
4.  Capture and post a log file per the instructions at
http://wiki.winehq.org/FAQ#get_log.

Does this program run without this error in Wine-1.3.19?

James McKenzie

jjmckenzie wrote:
> Not a clue and cannot even begin to help given the information you
provided.
> 
> 1.  Linux Distribution and Version.
> 2.  What is the name of the Program you are running.
> 3.  Video card and driver version.
> 4.  Capture and post a log file per the instructions at
> http://wiki.winehq.org/FAQ#get_log.
> 
> Does this program run without this error in Wine-1.3.19?
> 
> James McKenzie

Ubuntu 11.04 64 bit
Demon Stone (GOG version - released May 2011)
Nvidia GeForce 8400M GS, Driver 270.41.06
Log files available @ Bug 27091

I received this error in 1.3.19 as well. 

The game was just re-released digitally this month on GOG and is DRM-free. The
*retail* version worked with a no-cd crack in 1.3.0. (I was able to run the
retail version in Ubuntu 10.10 although I don't remember the Wine version)

One other user was kind enough to enter test results for Fedora 14. He was able
to play the GOG version without this crash.

I installed 1.3.20 from PPA. In addition I've compiled Wine 1.3.20 and ran
the game from the 1.3.20 build directory. Both caused the same crash.

It might be distro related but I didn't see anything Wine related in the
reported bugs for Ubuntu 11.04..

The only concrete information that I have is that page fault. I need some help
on determining what's causing it. What's my next step?

perryh wrote:
> "dk" <wineforum-user at winehq.org> wrote:
> 
> Does it work any better if you cd to the program directory before
> running it?
> 
> cd
> 
> cd '.wine-ds/drive_c/Program Files/Demon Stone'
> 
> env WINEPREFIX=~/.wine-ds wine demonlaunch.exe &>
~/logs/demonstone_1_3_20.txt

Yes, it does!  How did you know to suggest that?

I'm really confused why it would cause a page fault with only this game but
other games (run via similar commands) all worked fine.

Thanks - that really helped! :)

On Fri, May 20, 2011 at 07:52, dk <wineforum-user at winehq.org>
wrote:
>
> perryh wrote:
>
> Yes, it does! ?How did you know to suggest that?
Maybe by reading the FAQ section "Running Applications"...

perryh wrote:
> "dk" <wineforum-user at winehq.org> wrote:
> 
> 
> > 
> > > Does it work any better if you cd to the program directory
> > > before running it?
> > > 
> > 
> > Yes, it does!  How did you know to suggest that?
> > 
> 
> It's one of the things one learns after reading this forum/mailing
> list for a while.  When starting a program, Windows normally sets
> the current directory to the program's location.  (One might well
> ask, why does Wine not do the same?)
> 
> 
> > I'm really confused why it would cause a page fault with only this
> > game but other games (run via similar commands) all worked fine.
> > 
> 
> Some Windows programs seem to be more tolerant than others :)

Well, I would like to clarify about "mre tolerant than others"..

The reality is that you cannot measure tolerance of app. Either it is or it is
not. Thats it. WHy,, you may ask?

The answer simply lays under the fgact that each and every automated testing
platform must perform additional checks that depends of path of the any binary
you want to execute. Example can be taken for application that is intended to:

- Work in one desktop - one session - one user mode ( a.k.a Windows OS ). Once
you change any of those core elemnts to "multi xxx", you are now
hitting the effect of what users threat as "tolerance". From
developers view of point, it is nothing more as checks that makes sure you runb
and threat application in the EXCAT use-case application is intended for.

Hope you get the idea.