http://bugs.winehq.org/show_bug.cgi?id=20986
--- Comment #12 from Steve Zalek zaleksf@umich.edu 2009-12-14 20:27:39 --- (In reply to comment #9)
The log you attached does not contain any attempt of starting maxima.exe so i fear it's useless for now. I decided to download the app, and i can confirm there seems to be a bug. However , could you give the the exact steps to reproduce this bug?
A guess what could go wrong: 0030:Starting process L"C:\Program Files\Euler\maxima.exe" (entryproc=0x401240) . . 0030:Call KERNEL32.VirtualAlloc(110a0000,2ef60000,00002000,00000001) ret=0046d36a 0030:Ret KERNEL32.VirtualAlloc() retval=00000000 ret=0046d36a . .
You are correct - the log file was created upon Euler.exe initiation within Wine. There is no issue with Euler itself. The issue is with maxima.exe; I don't know how to have the debugger keep recording throughout the series of actions that causes the problem.
The problem is caused by calling maxima.exe. This is done within Euler by executing a command that uses the maxima command prompt ("::") instead of the Euler command prompt, to solve a problem. Please see the "App screenshot showing error" file that I uploaded as an example of the problem.
I have run ~$WINEDEBUG=+relay,+seh,+tid wine 'C:\Program Files\Euler\maxima.exe' >& log-with-maxima-start.txt in an attempt to capture the issue with starting maxima, and uploaded the file. Hope this helps.
SZ