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 crash dump it crashes in the 3D driver, which is rather suspicious. It could be a driver bug, or a case of an multithreaded d3d ap. Can you make a ddraw,d3d7,tid trace?
As requested I traced wine with
export WINEDEBUG=+ddraw,+d3d7,+tid ./wine "C:\CSoft\Matheland2\Mathe2.exe" &>trace+ddraw+d3d7+tid.txt
It looks like as if wine crashes instantly when calling the first d3d functions.
Regards,
Klaus