[Bug 311] Changed - Wine do not execute several programs - err:module:map_image

wine-bugs at winehq.com wine-bugs at winehq.com
Thu Apr 25 07:28:11 CDT 2002


http://bugs.codeweavers.com/show_bug.cgi?id=311

*** shadow/311	Thu Apr 25 01:46:35 2002
--- shadow/311.tmp.9592	Thu Apr 25 07:28:11 2002
***************
*** 179,181 ****
--- 179,212 ----
  But by this problem suffer only 10% windows programs. One of them is attached to 
  this report. I have kernel 2.2.19
  What additional test would you like to do from me?
+ 
+ ------- Additional Comments From apa3a at yahoo.com  2002-04-25 07:28 -------
+ Jaroslav, you are really patient with me :-)
+ 
+ Ok, now diving in Wine internals.
+ As I already mentioned I was not able to reproduce the bug on my machine.
+ You are welcome to try to do research on your own. 
+ "The Perfect Enduser Wine Debugging Guide" can help you in this:
+ http://wine.codeweavers.com/fom-meta/cache/230.html
+ 
+ Refresh and do clean wine reinstall with default settings.
+ Get relay trace from successful program run (when the drive type is "floppy"),
+ then when the app crashes (drive type is "hd"). Separate from the successful run
+ the portion of trace which corresponds to failed trace and find differences
+ between them. Probably the most important information will be in differences
+ near crash place.
+ 
+ You can find information about this and other debugging methods in this chapter
+ of "The Perfect Enduser Wine Debugging Guide":
+ http://wine.codeweavers.com/fom-meta/cache/265.html
+ 
+ I advise you to start with relay trace of this channels (sorry for the line
+ wrapping):
+ wine --debugmsg
+ +file,+dll,+dosfs,+elfdll,+exec,+loaddll,+module,+process,+relay,+win32 app.exe
+ &> 1.log
+ 
+ To get *all* debugging messages run it as:
+ wine --debugmsg +all app.exe &> 1.log
+ 
+ Let me know if you have any questions.
\ No newline at end of file



More information about the wine-bugs mailing list